Sharing and using passes or accounts

ABSTRACT

The present disclosure generally relates to a computer system displaying user interfaces for accessing passes and transfer accounts. In some examples, passes are added to the computer system. In some examples, passes are accessed. In some examples, transfers relating to the passes and transfer accounts are displayed, such as in search user interfaces.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application claims the benefit of U.S. Provisional Application Ser.No. 63/032,504, filed May 29, 2020, entitled “SHARING AND USING PASSESOR ACCOUNTS” and U.S. Provisional Application Ser. No. 63/041,996, filedJun. 21, 2020, entitled “SHARING AND USING PASSES OR ACCOUNTS”, theentire contents of which are hereby incorporated by reference.

FIELD

The present disclosure relates generally to computer user interfaces,and more specifically to interfaces and techniques for sharing and usingpasses or accounts.

BACKGROUND

A computer system can be used to access information related to a pass oran account. The information can then be used to provide goods orservices to a user, such as gaining entry to a venue or transferringfunds. Typically, the information related to the pass or to the accountis associated with a user of the computer system.

BRIEF SUMMARY

Some techniques for using passes or accounts using computer systems,however, are generally cumbersome and inefficient. For example, someexisting techniques provide limited options for sharing a pass withanother user. In addition, some existing techniques use a complex andtime-consuming user interface to use a pass or account, which mayinclude multiple key presses or keystrokes. Existing techniques requiremore time than necessary, wasting user time and device energy. Thislatter consideration is particularly important in battery-operateddevices.

Accordingly, the present technique provides computer systems withfaster, more efficient methods and interfaces for sharing and usingpasses or accounts. Such methods and interfaces optionally complement orreplace other methods for using passes or accounts. Such methods andinterfaces reduce the cognitive burden on a user and produce a moreefficient human-machine interface. For battery-operated computingdevices, such methods and interfaces conserve power and increase thetime between battery charges.

Example methods are disclosed herein. An example method includes, at acomputer system that is in communication with a display generationcomponent and one or more input devices: displaying, via the displaygeneration component, a first user interface that includes informationabout one or more passes associated with a service provider; whiledisplaying the first user interface, receiving, via the one or moreinput devices, a request to add one or more passes to an accountassociated with a first user identity, wherein the one or more passesprovide access to a service provided by the service provider; afterreceiving the request, displaying, via the display generation component,a share affordance for providing at least one of the one or more passesto an account associated with a second user identity; receiving, via theone or more input devices, a user input corresponding to selection ofthe share affordance; and in response to receiving the user inputcorresponding to selection of the share affordance, initiating a processfor providing at least one of the one or more passes to the accountassociated with the second user identity.

Example non-transitory computer-readable storage media are describedherein. An example non-transitory computer-readable storage mediumstores one or more programs configured to be executed by one or moreprocessors of a computer system that is in communication with a displaygeneration component and one or more input devices, the one or moreprograms including instructions for: displaying, via the displaygeneration component, a first user interface that includes informationabout one or more passes associated with a service provider; whiledisplaying the first user interface, receiving, via the one or moreinput devices, a request to add one or more passes to an accountassociated with a first user identity, wherein the one or more passesprovide access to a service provided by the service provider; afterreceiving the request, displaying, via the display generation component,a share affordance for providing at least one of the one or more passesto an account associated with a second user identity; receiving, via theone or more input devices, a user input corresponding to selection ofthe share affordance; and in response to receiving the user inputcorresponding to selection of the share affordance, initiating a processfor providing at least one of the one or more passes to the accountassociated with the second user identity.

Example transitory computer-readable storage media are described herein.An example transitory computer-readable storage medium stores one ormore programs configured to be executed by one or more processors of acomputer system that is in communication with a display generationcomponent and one or more input devices, the one or more programsincluding instructions for: displaying, via the display generationcomponent, a first user interface that includes information about one ormore passes associated with a service provider; while displaying thefirst user interface, receiving, via the one or more input devices, arequest to add one or more passes to an account associated with a firstuser identity, wherein the one or more passes provide access to aservice provided by the service provider; after receiving the request,displaying, via the display generation component, a share affordance forproviding at least one of the one or more passes to an accountassociated with a second user identity; receiving, via the one or moreinput devices, a user input corresponding to selection of the shareaffordance; and in response to receiving the user input corresponding toselection of the share affordance, initiating a process for providing atleast one of the one or more passes to the account associated with thesecond user identity.

Example computer systems are described herein. An example computersystem includes a display generation component; one or more inputdevices; one or more processors; and memory storing one or more programsconfigured to be executed by the one or more processors, the one or moreprograms including instructions for: displaying, via the displaygeneration component, a first user interface that includes informationabout one or more passes associated with a service provider; whiledisplaying the first user interface, receiving, via the one or moreinput devices, a request to add one or more passes to an accountassociated with a first user identity, wherein the one or more passesprovide access to a service provided by the service provider; afterreceiving the request, displaying, via the display generation component,a share affordance for providing at least one of the one or more passesto an account associated with a second user identity; receiving, via theone or more input devices, a user input corresponding to selection ofthe share affordance; and in response to receiving the user inputcorresponding to selection of the share affordance, initiating a processfor providing at least one of the one or more passes to the accountassociated with the second user identity.

An example computer system includes: a display generation component; oneor more input devices; means for displaying, via the display generationcomponent, a first user interface that includes information about one ormore passes associated with a service provider; means for, whiledisplaying the first user interface, receiving, via the one or moreinput devices, a request to add one or more passes to an accountassociated with a first user identity, wherein the one or more passesprovide access to a service provided by the service provider; means for,after receiving the request, displaying, via the display generationcomponent, a share affordance for providing at least one of the one ormore passes to an account associated with a second user identity; meansfor receiving, via the one or more input devices, a user inputcorresponding to selection of the share affordance; and means for, inresponse to receiving the user input corresponding to selection of theshare affordance, initiating a process for providing at least one of theone or more passes to the account associated with the second useridentity.

Example methods are disclosed herein. An example method includes, at acomputer system that is in communication with a display generationcomponent and one or more input devices: detecting that datacorresponding to a first pass was provided by the computer system to apass reader terminal that is separate from the computer system; afterdetecting that data corresponding to the first pass was provided by thecomputer system to the pass reader terminal: displaying, via the displaygeneration component, an indication that data corresponding to the firstpass was provided by the computer system to the pass reader terminal; inaccordance with a determination that data corresponding to a second passis available to be provided to the pass reader terminal by the computersystem, providing a prompt to the user to provide authorization for datacorresponding to the second pass to be provided to the pass readerterminal by the computer system; and in accordance with a determinationthat data corresponding to a second pass is not available to be providedto the pass reader terminal by the computer system, forgoing providingthe prompt to the user to provide authorization for data correspondingto a second pass to be provided to the pass reader terminal by thecomputer system.

Example non-transitory computer-readable storage media are describedherein. An example non-transitory computer-readable storage mediumstores one or more programs configured to be executed by one or moreprocessors of a computer system that is in communication with a displaygeneration component and one or more input devices, the one or moreprograms including instructions for: detecting that data correspondingto a first pass was provided by the computer system to a pass readerterminal that is separate from the computer system; after detecting thatdata corresponding to the first pass was provided by the computer systemto the pass reader terminal: displaying, via the display generationcomponent, an indication that data corresponding to the first pass wasprovided by the computer system to the pass reader terminal; inaccordance with a determination that data corresponding to a second passis available to be provided to the pass reader terminal by the computersystem, providing a prompt to the user to provide authorization for datacorresponding to the second pass to be provided to the pass readerterminal by the computer system; and in accordance with a determinationthat data corresponding to a second pass is not available to be providedto the pass reader terminal by the computer system, forgoing providingthe prompt to the user to provide authorization for data correspondingto a second pass to be provided to the pass reader terminal by thecomputer system.

Example transitory computer-readable storage media are described herein.An example transitory computer-readable storage medium stores one ormore programs configured to be executed by one or more processors of acomputer system that is in communication with a display generationcomponent and one or more input devices, the one or more programsincluding instructions for: detecting that data corresponding to a firstpass was provided by the computer system to a pass reader terminal thatis separate from the computer system; after detecting that datacorresponding to the first pass was provided by the computer system tothe pass reader terminal: displaying, via the display generationcomponent, an indication that data corresponding to the first pass wasprovided by the computer system to the pass reader terminal; inaccordance with a determination that data corresponding to a second passis available to be provided to the pass reader terminal by the computersystem, providing a prompt to the user to provide authorization for datacorresponding to the second pass to be provided to the pass readerterminal by the computer system; and in accordance with a determinationthat data corresponding to a second pass is not available to be providedto the pass reader terminal by the computer system, forgoing providingthe prompt to the user to provide authorization for data correspondingto a second pass to be provided to the pass reader terminal by thecomputer system.

Example computer systems are described herein. An example computersystem includes a display generation component; one or more inputdevices; one or more processors; and memory storing one or more programsconfigured to be executed by the one or more processors, the one or moreprograms including instructions for: detecting that data correspondingto a first pass was provided by the computer system to a pass readerterminal that is separate from the computer system; after detecting thatdata corresponding to the first pass was provided by the computer systemto the pass reader terminal: displaying, via the display generationcomponent, an indication that data corresponding to the first pass wasprovided by the computer system to the pass reader terminal; inaccordance with a determination that data corresponding to a second passis available to be provided to the pass reader terminal by the computersystem, providing a prompt to the user to provide authorization for datacorresponding to the second pass to be provided to the pass readerterminal by the computer system; and in accordance with a determinationthat data corresponding to a second pass is not available to be providedto the pass reader terminal by the computer system, forgoing providingthe prompt to the user to provide authorization for data correspondingto a second pass to be provided to the pass reader terminal by thecomputer system.

An example computer system includes: a display generation component; oneor more input devices; means for detecting that data corresponding to afirst pass was provided by the computer system to a pass reader terminalthat is separate from the computer system; means for, after detectingthat data corresponding to the first pass was provided by the computersystem to the pass reader terminal: displaying, via the displaygeneration component, an indication that data corresponding to the firstpass was provided by the computer system to the pass reader terminal;means for, in accordance with a determination that data corresponding toa second pass is available to be provided to the pass reader terminal bythe computer system, providing a prompt to the user to provideauthorization for data corresponding to the second pass to be providedto the pass reader terminal by the computer system; and means for, inaccordance with a determination that data corresponding to a second passis not available to be provided to the pass reader terminal by thecomputer system, forgoing providing the prompt to the user to provideauthorization for data corresponding to a second pass to be provided tothe pass reader terminal by the computer system.

Example methods are disclosed herein. An example method includes, at acomputer system that is in communication with a display generationcomponent and one or more input devices: displaying, via the displaygeneration component, a first user interface including an indication ofan account; receiving, via the one or more input devices, authenticationdata; and in response to receiving the authentication data: inaccordance with a determination that the authentication data satisfiesauthentication criteria associated with the account, displaying, via thedisplay generation component, a first machine-readable code associatedwith the account; and in accordance with a determination that theauthentication data does not satisfy the authentication criteriaassociated with the account, forgoing display of the firstmachine-readable code associated with the account.

Example non-transitory computer-readable storage media are describedherein. An example non-transitory computer-readable storage mediumstores one or more programs configured to be executed by one or moreprocessors of a computer system that is in communication with a displaygeneration component and one or more input devices, the one or moreprograms including instructions for: displaying, via the displaygeneration component, a first user interface including an indication ofan account; receiving, via the one or more input devices, authenticationdata; and in response to receiving the authentication data: inaccordance with a determination that the authentication data satisfiesauthentication criteria associated with the account, displaying, via thedisplay generation component, a first machine-readable code associatedwith the account; and in accordance with a determination that theauthentication data does not satisfy the authentication criteriaassociated with the account, forgoing display of the firstmachine-readable code associated with the account.

Example transitory computer-readable storage media are described herein.An example transitory computer-readable storage medium stores one ormore programs configured to be executed by one or more processors of acomputer system that is in communication with a display generationcomponent and one or more input devices, the one or more programsincluding instructions for: displaying, via the display generationcomponent, a first user interface including an indication of an account;receiving, via the one or more input devices, authentication data; andin response to receiving the authentication data: in accordance with adetermination that the authentication data satisfies authenticationcriteria associated with the account, displaying, via the displaygeneration component, a first machine-readable code associated with theaccount; and in accordance with a determination that the authenticationdata does not satisfy the authentication criteria associated with theaccount, forgoing display of the first machine-readable code associatedwith the account.

Example computer systems are described herein. An example computersystem includes a display generation component; one or more inputdevices; one or more processors; and memory storing one or more programsconfigured to be executed by the one or more processors, the one or moreprograms including instructions for: displaying, via the displaygeneration component, a first user interface including an indication ofan account; receiving, via the one or more input devices, authenticationdata; and in response to receiving the authentication data: inaccordance with a determination that the authentication data satisfiesauthentication criteria associated with the account, displaying, via thedisplay generation component, a first machine-readable code associatedwith the account; and in accordance with a determination that theauthentication data does not satisfy the authentication criteriaassociated with the account, forgoing display of the firstmachine-readable code associated with the account.

An example computer system includes: a display generation component; oneor more input devices; means for displaying, via the display generationcomponent, a first user interface including an indication of an account;means for receiving, via the one or more input devices, authenticationdata; and means for, in response to receiving the authentication data:in accordance with a determination that the authentication datasatisfies authentication criteria associated with the account,displaying, via the display generation component, a firstmachine-readable code associated with the account; and in accordancewith a determination that the authentication data does not satisfy theauthentication criteria associated with the account, forgoing display ofthe first machine-readable code associated with the account.

Example methods are disclosed herein. An example method includes, at acomputer system that is in communication with a display generationcomponent and one or more input devices: displaying, via the displaygeneration component, an account user interface that includes aplurality of visual representations of a plurality of differentaccounts; while displaying the account user interface, receiving, viathe one or more input devices, a scroll input corresponding to a requestto scroll the account user interface; in response to receiving thescroll input, scrolling, via the display generation component, theaccount user interface to cause a first visual representation of a firstaccount and a second visual representation of a second account toscroll; and subsequent to receiving the scroll input and whiledisplaying the account user interface: in accordance with adetermination that the first visual representation of the first accountsatisfies a set of selection criteria, the set of selection criteriaincludes a criterion that is met when the first visual representation ofthe first account is displayed in a selection region for at least athreshold amount of time, reducing a visual emphasis of the secondvisual representation of the second account relative to a visualemphasis of the first visual representation of the first account; and inaccordance with a determination that the second visual representation ofthe second account satisfies the set of selection criteria, reducing avisual emphasis of the first visual representation of the first accountrelative to a visual emphasis of the second visual representation of thesecond account.

Example non-transitory computer-readable storage media are describedherein. An example non-transitory computer-readable storage mediumstores one or more programs configured to be executed by one or moreprocessors of a computer system that is in communication with a displaygeneration component and one or more input devices, the one or moreprograms including instructions for: displaying, via the displaygeneration component, an account user interface that includes aplurality of visual representations of a plurality of differentaccounts; while displaying the account user interface, receiving, viathe one or more input devices, a scroll input corresponding to a requestto scroll the account user interface; in response to receiving thescroll input, scrolling, via the display generation component, theaccount user interface to cause a first visual representation of a firstaccount and a second visual representation of a second account toscroll; and subsequent to receiving the scroll input and whiledisplaying the account user interface: in accordance with adetermination that the first visual representation of the first accountsatisfies a set of selection criteria, the set of selection criteriaincludes a criterion that is met when the first visual representation ofthe first account is displayed in a selection region for at least athreshold amount of time, reducing a visual emphasis of the secondvisual representation of the second account relative to a visualemphasis of the first visual representation of the first account; and inaccordance with a determination that the second visual representation ofthe second account satisfies the set of selection criteria, reducing avisual emphasis of the first visual representation of the first accountrelative to a visual emphasis of the second visual representation of thesecond account.

Example transitory computer-readable storage media are described herein.An example transitory computer-readable storage medium stores one ormore programs configured to be executed by one or more processors of acomputer system that is in communication with a display generationcomponent and one or more input devices, the one or more programsincluding instructions for: displaying, via the display generationcomponent, an account user interface that includes a plurality of visualrepresentations of a plurality of different accounts; while displayingthe account user interface, receiving, via the one or more inputdevices, a scroll input corresponding to a request to scroll the accountuser interface; in response to receiving the scroll input, scrolling,via the display generation component, the account user interface tocause a first visual representation of a first account and a secondvisual representation of a second account to scroll; and subsequent toreceiving the scroll input and while displaying the account userinterface: in accordance with a determination that the first visualrepresentation of the first account satisfies a set of selectioncriteria, the set of selection criteria includes a criterion that is metwhen the first visual representation of the first account is displayedin a selection region for at least a threshold amount of time, reducinga visual emphasis of the second visual representation of the secondaccount relative to a visual emphasis of the first visual representationof the first account; and in accordance with a determination that thesecond visual representation of the second account satisfies the set ofselection criteria, reducing a visual emphasis of the first visualrepresentation of the first account relative to a visual emphasis of thesecond visual representation of the second account.

Example computer systems are described herein. An example computersystem includes a display generation component; one or more inputdevices; one or more processors; and memory storing one or more programsconfigured to be executed by the one or more processors, the one or moreprograms including instructions for: displaying, via the displaygeneration component, an account user interface that includes aplurality of visual representations of a plurality of differentaccounts; while displaying the account user interface, receiving, viathe one or more input devices, a scroll input corresponding to a requestto scroll the account user interface; in response to receiving thescroll input, scrolling, via the display generation component, theaccount user interface to cause a first visual representation of a firstaccount and a second visual representation of a second account toscroll; and subsequent to receiving the scroll input and whiledisplaying the account user interface: in accordance with adetermination that the first visual representation of the first accountsatisfies a set of selection criteria, the set of selection criteriaincludes a criterion that is met when the first visual representation ofthe first account is displayed in a selection region for at least athreshold amount of time, reducing a visual emphasis of the secondvisual representation of the second account relative to a visualemphasis of the first visual representation of the first account; and inaccordance with a determination that the second visual representation ofthe second account satisfies the set of selection criteria, reducing avisual emphasis of the first visual representation of the first accountrelative to a visual emphasis of the second visual representation of thesecond account.

An example computer system includes: a display generation component; oneor more input devices; means for displaying, via the display generationcomponent, an account user interface that includes a plurality of visualrepresentations of a plurality of different accounts; means for, whiledisplaying the account user interface, receiving, via the one or moreinput devices, a scroll input corresponding to a request to scroll theaccount user interface; means for, in response to receiving the scrollinput, scrolling, via the display generation component, the account userinterface to cause a first visual representation of a first account anda second visual representation of a second account to scroll; and meansfor, subsequent to receiving the scroll input and while displaying theaccount user interface: in accordance with a determination that thefirst visual representation of the first account satisfies a set ofselection criteria, the set of selection criteria includes a criterionthat is met when the first visual representation of the first account isdisplayed in a selection region for at least a threshold amount of time,reducing a visual emphasis of the second visual representation of thesecond account relative to a visual emphasis of the first visualrepresentation of the first account; and in accordance with adetermination that the second visual representation of the secondaccount satisfies the set of selection criteria, reducing a visualemphasis of the first visual representation of the first accountrelative to a visual emphasis of the second visual representation of thesecond account.

Example methods are disclosed herein. An example method includes, at acomputer system that is in communication with a display generationcomponent and one or more input devices: receiving, via the one or moreinput devices, a first input; in response to receiving the first input:displaying, via the display generation component, an account userinterface that includes a first visual representation of a firstaccount; while displaying the first visual representation of the firstaccount, receiving, via the one or more input devices, a second inputcorresponding to selection of the first visual representation of thefirst account; and in response to receiving the second inputcorresponding to selection of the first visual representation of thefirst account: in accordance with a determination that the first visualrepresentation of the first account was displayed in response to arequest to prepare one or more accounts from the account user interfacefor use, displaying, via the display generation component, a readableportion of a machine-readable code corresponding to the first account;and in accordance with a determination that the first visualrepresentation of the first account was displayed in response to arequest to view information about one or more accounts without preparingthe one or more accounts from the account user interface for use,displaying, via the display generation component, informationcorresponding to the first account without displaying the readableportion of the machine-readable code corresponding to the first account.

Example non-transitory computer-readable storage media are describedherein. An example non-transitory computer-readable storage mediumstores one or more programs configured to be executed by one or moreprocessors of a computer system that is in communication with a displaygeneration component and one or more input devices, the one or moreprograms including instructions for: receiving, via the one or moreinput devices, a first input; in response to receiving the first input:displaying, via the display generation component, an account userinterface that includes a first visual representation of a firstaccount; while displaying the first visual representation of the firstaccount, receiving, via the one or more input devices, a second inputcorresponding to selection of the first visual representation of thefirst account; and in response to receiving the second inputcorresponding to selection of the first visual representation of thefirst account: in accordance with a determination that the first visualrepresentation of the first account was displayed in response to arequest to prepare one or more accounts from the account user interfacefor use, displaying, via the display generation component, a readableportion of a machine-readable code corresponding to the first account;and in accordance with a determination that the first visualrepresentation of the first account was displayed in response to arequest to view information about one or more accounts without preparingthe one or more accounts from the account user interface for use,displaying, via the display generation component, informationcorresponding to the first account without displaying the readableportion of the machine-readable code corresponding to the first account.

Example transitory computer-readable storage media are described herein.An example transitory computer-readable storage medium stores one ormore programs configured to be executed by one or more processors of acomputer system that is in communication with a display generationcomponent and one or more input devices, the one or more programsincluding instructions for: receiving, via the one or more inputdevices, a first input; in response to receiving the first input:displaying, via the display generation component, an account userinterface that includes a first visual representation of a firstaccount; while displaying the first visual representation of the firstaccount, receiving, via the one or more input devices, a second inputcorresponding to selection of the first visual representation of thefirst account; and in response to receiving the second inputcorresponding to selection of the first visual representation of thefirst account: in accordance with a determination that the first visualrepresentation of the first account was displayed in response to arequest to prepare one or more accounts from the account user interfacefor use, displaying, via the display generation component, a readableportion of a machine-readable code corresponding to the first account;and in accordance with a determination that the first visualrepresentation of the first account was displayed in response to arequest to view information about one or more accounts without preparingthe one or more accounts from the account user interface for use,displaying, via the display generation component, informationcorresponding to the first account without displaying the readableportion of the machine-readable code corresponding to the first account.

Example computer systems are described herein. An example computersystem includes a display generation component; one or more inputdevices; one or more processors; and memory storing one or more programsconfigured to be executed by the one or more processors, the one or moreprograms including instructions for: receiving, via the one or moreinput devices, a first input; in response to receiving the first input:displaying, via the display generation component, an account userinterface that includes a first visual representation of a firstaccount; while displaying the first visual representation of the firstaccount, receiving, via the one or more input devices, a second inputcorresponding to selection of the first visual representation of thefirst account; and in response to receiving the second inputcorresponding to selection of the first visual representation of thefirst account: in accordance with a determination that the first visualrepresentation of the first account was displayed in response to arequest to prepare one or more accounts from the account user interfacefor use, displaying, via the display generation component, a readableportion of a machine-readable code corresponding to the first account;and in accordance with a determination that the first visualrepresentation of the first account was displayed in response to arequest to view information about one or more accounts without preparingthe one or more accounts from the account user interface for use,displaying, via the display generation component, informationcorresponding to the first account without displaying the readableportion of the machine-readable code corresponding to the first account.

An example computer system includes: a display generation component; oneor more input devices; means for receiving, via the one or more inputdevices, a first input; means for, in response to receiving the firstinput: displaying, via the display generation component, an account userinterface that includes a first visual representation of a firstaccount; means for, while displaying the first visual representation ofthe first account, receiving, via the one or more input devices, asecond input corresponding to selection of the first visualrepresentation of the first account; and means for, in response toreceiving the second input corresponding to selection of the firstvisual representation of the first account: in accordance with adetermination that the first visual representation of the first accountwas displayed in response to a request to prepare one or more accountsfrom the account user interface for use, displaying, via the displaygeneration component, a readable portion of a machine-readable codecorresponding to the first account; and in accordance with adetermination that the first visual representation of the first accountwas displayed in response to a request to view information about one ormore accounts without preparing the one or more accounts from theaccount user interface for use, displaying, via the display generationcomponent, information corresponding to the first account withoutdisplaying the readable portion of the machine-readable codecorresponding to the first account.

Example methods are disclosed herein. An example method includes, at acomputer system that is in communication with a display generationcomponent and one or more input devices: displaying, via the displaygeneration component, a search user interface; while displaying thesearch user interface, receiving, via the one or more input devices,input that includes a search term; and in response to receiving theinput that includes the search term: in accordance with a determinationthat the search user interface corresponds to a plurality of transferaccounts provisioned on the computer system and configured to transfer aresource of the respective transfer account upon user authorization:concurrently displaying, via the display generation component, aplurality of search results selected using the search term, theplurality of search results including: a first search resultcorresponding to a resource transfer activity of a first account of theplurality of transfer accounts, and a second search result correspondingto a resource transfer activity of a second account, different from thefirst account, of the plurality of transfer accounts.

Example non-transitory computer-readable storage media are describedherein. An example non-transitory computer-readable storage mediumstores one or more programs configured to be executed by one or moreprocessors of a computer system that is in communication with a displaygeneration component and one or more input devices, the one or moreprograms including instructions for: displaying, via the displaygeneration component, a search user interface; while displaying thesearch user interface, receiving, via the one or more input devices,input that includes a search term; and in response to receiving theinput that includes the search term: in accordance with a determinationthat the search user interface corresponds to a plurality of transferaccounts provisioned on the computer system and configured to transfer aresource of the respective transfer account upon user authorization:concurrently displaying, via the display generation component, aplurality of search results selected using the search term, theplurality of search results including: a first search resultcorresponding to a resource transfer activity of a first account of theplurality of transfer accounts, and a second search result correspondingto a resource transfer activity of a second account, different from thefirst account, of the plurality of transfer accounts.

Example transitory computer-readable storage media are described herein.An example transitory computer-readable storage medium stores one ormore programs configured to be executed by one or more processors of acomputer system that is in communication with a display generationcomponent and one or more input devices, the one or more programsincluding instructions for: displaying, via the display generationcomponent, a search user interface; while displaying the search userinterface, receiving, via the one or more input devices, input thatincludes a search term; and in response to receiving the input thatincludes the search term: in accordance with a determination that thesearch user interface corresponds to a plurality of transfer accountsprovisioned on the computer system and configured to transfer a resourceof the respective transfer account upon user authorization: concurrentlydisplaying, via the display generation component, a plurality of searchresults selected using the search term, the plurality of search resultsincluding: a first search result corresponding to a resource transferactivity of a first account of the plurality of transfer accounts, and asecond search result corresponding to a resource transfer activity of asecond account, different from the first account, of the plurality oftransfer accounts.

Example computer systems are described herein. An example computersystem includes a display generation component; one or more inputdevices; one or more processors; and memory storing one or more programsconfigured to be executed by the one or more processors, the one or moreprograms including instructions for: displaying, via the displaygeneration component, a search user interface; while displaying thesearch user interface, receiving, via the one or more input devices,input that includes a search term; and in response to receiving theinput that includes the search term: in accordance with a determinationthat the search user interface corresponds to a plurality of transferaccounts provisioned on the computer system and configured to transfer aresource of the respective transfer account upon user authorization:concurrently displaying, via the display generation component, aplurality of search results selected using the search term, theplurality of search results including: a first search resultcorresponding to a resource transfer activity of a first account of theplurality of transfer accounts, and a second search result correspondingto a resource transfer activity of a second account, different from thefirst account, of the plurality of transfer accounts.

An example computer system includes: a display generation component; oneor more input devices; means for displaying, via the display generationcomponent, a search user interface; means for, while displaying thesearch user interface, receiving, via the one or more input devices,input that includes a search term; and means for, in response toreceiving the input that includes the search term: in accordance with adetermination that the search user interface corresponds to a pluralityof transfer accounts provisioned on the computer system and configuredto transfer a resource of the respective transfer account upon userauthorization: concurrently displaying, via the display generationcomponent, a plurality of search results selected using the search term,the plurality of search results including: a first search resultcorresponding to a resource transfer activity of a first account of theplurality of transfer accounts, and a second search result correspondingto a resource transfer activity of a second account, different from thefirst account, of the plurality of transfer accounts.

Executable instructions for performing these functions are, optionally,included in a non-transitory computer-readable storage medium or othercomputer program product configured for execution by one or moreprocessors. Executable instructions for performing these functions are,optionally, included in a transitory computer-readable storage medium orother computer program product configured for execution by one or moreprocessors.

Thus, devices are provided with faster, more efficient methods andinterfaces for sharing and using passes or accounts, thereby increasingthe effectiveness, efficiency, and user satisfaction with such devices.Such methods and interfaces may complement or replace other methods forsharing and using passes and accounts.

DESCRIPTION OF THE FIGURES

For a better understanding of the various described embodiments,reference should be made to the Description of Embodiments below, inconjunction with the following drawings in which like reference numeralsrefer to corresponding parts throughout the figures.

FIG. 1A is a block diagram illustrating a portable multifunction devicewith a touch-sensitive display in accordance with some embodiments.

FIG. 1B is a block diagram illustrating exemplary components for eventhandling in accordance with some embodiments.

FIG. 2 illustrates a portable multifunction device having a touch screenin accordance with some embodiments.

FIG. 3 is a block diagram of an exemplary multifunction device with adisplay and a touch-sensitive surface in accordance with someembodiments.

FIG. 4A illustrates an exemplary user interface for a menu ofapplications on a portable multifunction device in accordance with someembodiments.

FIG. 4B illustrates an exemplary user interface for a multifunctiondevice with a touch-sensitive surface that is separate from the displayin accordance with some embodiments.

FIG. 5A illustrates a personal electronic device in accordance with someembodiments.

FIG. 5B is a block diagram illustrating a personal electronic device inaccordance with some embodiments.

FIGS. 6A-6F illustrate exemplary user interfaces for sharing one or morepasses in accordance with some embodiments.

FIG. 7 is a flow diagram illustrating a method for sharing one or morepasses in accordance with some embodiments.

FIGS. 8A-8F illustrate exemplary user interfaces for providing a promptto a user to provide authorization in accordance with some embodiments.

FIG. 9 is a flow diagram illustrating a method for providing a prompt toa user to provide authorization in accordance with some embodiments.

FIGS. 10A-10L illustrate exemplary user interfaces for displaying amachine-readable code in accordance with some embodiments.

FIG. 11 is a flow diagram illustrating a method for displaying amachine-readable code in accordance with some embodiments.

FIGS. 12A-12C illustrate exemplary user interfaces for displayingcomputer storage accounts in accordance with some embodiments.

FIGS. 13A-13AA illustrate exemplary user interfaces for displaying andauthorizing transfer storage accounts in accordance with someembodiments.

FIG. 14 is a flow diagram illustrating a method for displaying transferaccounts in accordance with some embodiments.

FIG. 15 is a flow diagram illustrating a method for authorizing transferaccounts in accordance with some embodiments.

FIGS. 16A-16C illustrate exemplary user interfaces for searching one ormore computer storage accounts in accordance with some embodiments.

FIGS. 17A-17N illustrate exemplary user interfaces for searching one ormore transfer storage accounts in accordance with some embodiments.

FIG. 18 is a flow diagram illustrating a method for searching one ormore transfer storage accounts in accordance with some embodiments.

DESCRIPTION OF EMBODIMENTS

The following description sets forth exemplary methods, parameters, andthe like. It should be recognized, however, that such description is notintended as a limitation on the scope of the present disclosure but isinstead provided as a description of exemplary embodiments.

There is a need for electronic devices that provide efficient methodsand interfaces for sharing and using passes or accounts. For example,when one or more passes are received, there is a need for a user toeasily and efficiently provide one or more of the passes to a seconduser. As another example, when one or more passes are being used, thereis a need for a user to easily and efficiently provide datacorresponding to the passes to a pass reader terminal. As anotherexample, when using an account for a transaction, there is a need for auser to easily and efficiently provide a machine-readable codeassociated with the account to conduct the transaction. Such techniquescan reduce the cognitive burden on a user who shares or uses passes oraccounts, thereby enhancing productivity. Further, such techniques canreduce processor and battery power otherwise wasted on redundant userinputs.

Below, FIGS. 1A-1B, 2, 3, 4A-4B, and 5A-5B provide a description ofexemplary devices for performing the techniques for sharing and usingpasses or accounts. FIGS. 6A-6F illustrate exemplary user interfaces forsharing one or more passes in accordance with some embodiments. FIG. 7is a flow diagram illustrating methods for sharing one or more passes inaccordance with some embodiments. The user interfaces in FIGS. 6A-6F areused to illustrate the processes described below, including theprocesses in FIG. 7. FIGS. 8A-8F illustrate exemplary user interfacesfor providing a prompt to a user to provide authorization in accordancewith some embodiments. FIG. 9 is a flow diagram illustrating methods forproviding a prompt to a user to provide authorization in accordance withsome embodiments. The user interfaces in FIGS. 8A-8F are used toillustrate the processes described below, including the processes inFIG. 9. FIGS. 10A-10L illustrate exemplary user interfaces fordisplaying a machine-readable code, in accordance with some embodiments.FIG. 11 is a flow diagram illustrating methods for displaying amachine-readable code in accordance with some embodiments. The userinterfaces in FIGS. 10A-10L are used to illustrate the processesdescribed below, including the processes in FIG. 11. FIGS. 12A-12Cillustrate exemplary user interfaces for displaying computer storageaccounts in accordance with some embodiments. FIGS. 13A-13AA illustrateexemplary user interfaces for displaying and authorizing transferaccounts in accordance with some embodiments. FIG. 14 is a flow diagramillustrating methods for displaying transfer accounts in accordance withsome embodiments. FIG. 15 is a flow diagram illustrating methods forauthorizing transfer accounts in accordance with some embodiments. Theuser interfaces in FIGS. 12A-12C and FIGS. 13A-13AA are used toillustrate the processes described below, including the processes inFIGS. 14 and 15. FIGS. 16A-16C illustrate exemplary user interfaces forsearching one or more computer storage accounts in accordance with someembodiments. FIGS. 17A-17N illustrate exemplary user interfaces forsearching one or more transfer accounts in accordance with someembodiments. FIG. 18 is a flow diagram illustrating methods forsearching one or more transfer accounts. The user interfaces in FIGS.16A-16C and FIGS. 17A-17N are used to illustrate the processes describedbelow, including the processes in FIG. 18.

Although the following description uses terms “first,” “second,” etc. todescribe various elements, these elements should not be limited by theterms. These terms are only used to distinguish one element fromanother. For example, a first touch could be termed a second touch, and,similarly, a second touch could be termed a first touch, withoutdeparting from the scope of the various described embodiments. The firsttouch and the second touch are both touches, but they are not the sametouch.

The terminology used in the description of the various describedembodiments herein is for the purpose of describing particularembodiments only and is not intended to be limiting. As used in thedescription of the various described embodiments and the appendedclaims, the singular forms “a,” “an,” and “the” are intended to includethe plural forms as well, unless the context clearly indicatesotherwise. It will also be understood that the term “and/or” as usedherein refers to and encompasses any and all possible combinations ofone or more of the associated listed items. It will be furtherunderstood that the terms “includes,” “including,” “comprises,” and/or“comprising,” when used in this specification, specify the presence ofstated features, integers, steps, operations, elements, and/orcomponents, but do not preclude the presence or addition of one or moreother features, integers, steps, operations, elements, components,and/or groups thereof.

The term “if” is, optionally, construed to mean “when” or “upon” or “inresponse to determining” or “in response to detecting,” depending on thecontext. Similarly, the phrase “if it is determined” or “if [a statedcondition or event] is detected” is, optionally, construed to mean “upondetermining” or “in response to determining” or “upon detecting [thestated condition or event]” or “in response to detecting [the statedcondition or event],” depending on the context.

Embodiments of electronic devices, user interfaces for such devices, andassociated processes for using such devices are described. In someembodiments, the device is a portable communications device, such as amobile telephone, that also contains other functions, such as PDA and/ormusic player functions. Exemplary embodiments of portable multifunctiondevices include, without limitation, the iPhone®, iPod Touch®, and iPad®devices from Apple Inc. of Cupertino, Calif. Other portable electronicdevices, such as laptops or tablet computers with touch-sensitivesurfaces (e.g., touch screen displays and/or touchpads), are,optionally, used. It should also be understood that, in someembodiments, the device is not a portable communications device, but isa desktop computer with a touch-sensitive surface (e.g., a touch screendisplay and/or a touchpad). In some embodiments, the electronic deviceis a computer system that is in communication (e.g., via wirelesscommunication, via wired communication) with a display generationcomponent. The display generation component is configured to providevisual output, such as display via a CRT display, display via an LEDdisplay, or display via image projection. In some embodiments, thedisplay generation component is integrated with the computer system. Insome embodiments, the display generation component is separate from thecomputer system. As used herein, “displaying” content includes causingto display the content (e.g., video data rendered or decoded by displaycontroller 156) by transmitting, via a wired or wireless connection,data (e.g., image data or video data) to an integrated or externaldisplay generation component to visually produce the content.

In the discussion that follows, an electronic device that includes adisplay and a touch-sensitive surface is described. It should beunderstood, however, that the electronic device optionally includes oneor more other physical user-interface devices, such as a physicalkeyboard, a mouse, and/or a joystick.

The device typically supports a variety of applications, such as one ormore of the following: a drawing application, a presentationapplication, a word processing application, a website creationapplication, a disk authoring application, a spreadsheet application, agaming application, a telephone application, a video conferencingapplication, an e-mail application, an instant messaging application, aworkout support application, a photo management application, a digitalcamera application, a digital video camera application, a web browsingapplication, a digital music player application, and/or a digital videoplayer application.

The various applications that are executed on the device optionally useat least one common physical user-interface device, such as thetouch-sensitive surface. One or more functions of the touch-sensitivesurface as well as corresponding information displayed on the deviceare, optionally, adjusted and/or varied from one application to the nextand/or within a respective application. In this way, a common physicalarchitecture (such as the touch-sensitive surface) of the deviceoptionally supports the variety of applications with user interfacesthat are intuitive and transparent to the user.

Attention is now directed toward embodiments of portable devices withtouch-sensitive displays. FIG. 1A is a block diagram illustratingportable multifunction device 100 with touch-sensitive display system112 in accordance with some embodiments. Touch-sensitive display 112 issometimes called a “touch screen” for convenience and is sometimes knownas or called a “touch-sensitive display system.” Device 100 includesmemory 102 (which optionally includes one or more computer-readablestorage mediums), memory controller 122, one or more processing units(CPUs) 120, peripherals interface 118, RF circuitry 108, audio circuitry110, speaker 111, microphone 113, input/output (I/O) subsystem 106,other input control devices 116, and external port 124. Device 100optionally includes one or more optical sensors 164. Device 100optionally includes one or more contact intensity sensors 165 fordetecting intensity of contacts on device 100 (e.g., a touch-sensitivesurface such as touch-sensitive display system 112 of device 100).Device 100 optionally includes one or more tactile output generators 167for generating tactile outputs on device 100 (e.g., generating tactileoutputs on a touch-sensitive surface such as touch-sensitive displaysystem 112 of device 100 or touchpad 355 of device 300). Thesecomponents optionally communicate over one or more communication busesor signal lines 103.

As used in the specification and claims, the term “intensity” of acontact on a touch-sensitive surface refers to the force or pressure(force per unit area) of a contact (e.g., a finger contact) on thetouch-sensitive surface, or to a substitute (proxy) for the force orpressure of a contact on the touch-sensitive surface. The intensity of acontact has a range of values that includes at least four distinctvalues and more typically includes hundreds of distinct values (e.g., atleast 256). Intensity of a contact is, optionally, determined (ormeasured) using various approaches and various sensors or combinationsof sensors. For example, one or more force sensors underneath oradjacent to the touch-sensitive surface are, optionally, used to measureforce at various points on the touch-sensitive surface. In someimplementations, force measurements from multiple force sensors arecombined (e.g., a weighted average) to determine an estimated force of acontact. Similarly, a pressure-sensitive tip of a stylus is, optionally,used to determine a pressure of the stylus on the touch-sensitivesurface. Alternatively, the size of the contact area detected on thetouch-sensitive surface and/or changes thereto, the capacitance of thetouch-sensitive surface proximate to the contact and/or changes thereto,and/or the resistance of the touch-sensitive surface proximate to thecontact and/or changes thereto are, optionally, used as a substitute forthe force or pressure of the contact on the touch-sensitive surface. Insome implementations, the substitute measurements for contact force orpressure are used directly to determine whether an intensity thresholdhas been exceeded (e.g., the intensity threshold is described in unitscorresponding to the substitute measurements). In some implementations,the substitute measurements for contact force or pressure are convertedto an estimated force or pressure, and the estimated force or pressureis used to determine whether an intensity threshold has been exceeded(e.g., the intensity threshold is a pressure threshold measured in unitsof pressure). Using the intensity of a contact as an attribute of a userinput allows for user access to additional device functionality that mayotherwise not be accessible by the user on a reduced-size device withlimited real estate for displaying affordances (e.g., on atouch-sensitive display) and/or receiving user input (e.g., via atouch-sensitive display, a touch-sensitive surface, or aphysical/mechanical control such as a knob or a button).

As used in the specification and claims, the term “tactile output”refers to physical displacement of a device relative to a previousposition of the device, physical displacement of a component (e.g., atouch-sensitive surface) of a device relative to another component(e.g., housing) of the device, or displacement of the component relativeto a center of mass of the device that will be detected by a user withthe user's sense of touch. For example, in situations where the deviceor the component of the device is in contact with a surface of a userthat is sensitive to touch (e.g., a finger, palm, or other part of auser's hand), the tactile output generated by the physical displacementwill be interpreted by the user as a tactile sensation corresponding toa perceived change in physical characteristics of the device or thecomponent of the device. For example, movement of a touch-sensitivesurface (e.g., a touch-sensitive display or trackpad) is, optionally,interpreted by the user as a “down click” or “up click” of a physicalactuator button. In some cases, a user will feel a tactile sensationsuch as an “down click” or “up click” even when there is no movement ofa physical actuator button associated with the touch-sensitive surfacethat is physically pressed (e.g., displaced) by the user's movements. Asanother example, movement of the touch-sensitive surface is, optionally,interpreted or sensed by the user as “roughness” of the touch-sensitivesurface, even when there is no change in smoothness of thetouch-sensitive surface. While such interpretations of touch by a userwill be subject to the individualized sensory perceptions of the user,there are many sensory perceptions of touch that are common to a largemajority of users. Thus, when a tactile output is described ascorresponding to a particular sensory perception of a user (e.g., an “upclick,” a “down click,” “roughness”), unless otherwise stated, thegenerated tactile output corresponds to physical displacement of thedevice or a component thereof that will generate the described sensoryperception for a typical (or average) user.

It should be appreciated that device 100 is only one example of aportable multifunction device, and that device 100 optionally has moreor fewer components than shown, optionally combines two or morecomponents, or optionally has a different configuration or arrangementof the components. The various components shown in FIG. 1A areimplemented in hardware, software, or a combination of both hardware andsoftware, including one or more signal processing and/orapplication-specific integrated circuits.

Memory 102 optionally includes high-speed random access memory andoptionally also includes non-volatile memory, such as one or moremagnetic disk storage devices, flash memory devices, or othernon-volatile solid-state memory devices. Memory controller 122optionally controls access to memory 102 by other components of device100.

Peripherals interface 118 can be used to couple input and outputperipherals of the device to CPU 120 and memory 102. The one or moreprocessors 120 run or execute various software programs and/or sets ofinstructions stored in memory 102 to perform various functions fordevice 100 and to process data. In some embodiments, peripheralsinterface 118, CPU 120, and memory controller 122 are, optionally,implemented on a single chip, such as chip 104. In some otherembodiments, they are, optionally, implemented on separate chips.

RF (radio frequency) circuitry 108 receives and sends RF signals, alsocalled electromagnetic signals. RF circuitry 108 converts electricalsignals to/from electromagnetic signals and communicates withcommunications networks and other communications devices via theelectromagnetic signals. RF circuitry 108 optionally includes well-knowncircuitry for performing these functions, including but not limited toan antenna system, an RF transceiver, one or more amplifiers, a tuner,one or more oscillators, a digital signal processor, a CODEC chipset, asubscriber identity module (SIM) card, memory, and so forth. RFcircuitry 108 optionally communicates with networks, such as theInternet, also referred to as the World Wide Web (WWW), an intranetand/or a wireless network, such as a cellular telephone network, awireless local area network (LAN) and/or a metropolitan area network(MAN), and other devices by wireless communication. The RF circuitry 108optionally includes well-known circuitry for detecting near fieldcommunication (NFC) fields, such as by a short-range communicationradio. The wireless communication optionally uses any of a plurality ofcommunications standards, protocols, and technologies, including but notlimited to Global System for Mobile Communications (GSM), Enhanced DataGSM Environment (EDGE), high-speed downlink packet access (HSDPA),high-speed uplink packet access (HSUPA), Evolution, Data-Only (EV-DO),HSPA, HSPA+, Dual-Cell HSPA (DC-HSPDA), long term evolution (LTE), nearfield communication (NFC), wideband code division multiple access(W-CDMA), code division multiple access (CDMA), time division multipleaccess (TDMA), Bluetooth, Bluetooth Low Energy (BTLE), Wireless Fidelity(Wi-Fi) (e.g., IEEE 802.11a, IEEE 802.11b, IEEE 802.11g, IEEE 802.11n,and/or IEEE 802.11ac), voice over Internet Protocol (VoIP), Wi-MAX, aprotocol for e-mail (e.g., Internet message access protocol (IMAP)and/or post office protocol (POP)), instant messaging (e.g., extensiblemessaging and presence protocol (XMPP), Session Initiation Protocol forInstant Messaging and Presence Leveraging Extensions (SIMPLE), InstantMessaging and Presence Service (IMPS)), and/or Short Message Service(SMS), or any other suitable communication protocol, includingcommunication protocols not yet developed as of the filing date of thisdocument.

Audio circuitry 110, speaker 111, and microphone 113 provide an audiointerface between a user and device 100. Audio circuitry 110 receivesaudio data from peripherals interface 118, converts the audio data to anelectrical signal, and transmits the electrical signal to speaker 111.Speaker 111 converts the electrical signal to human-audible sound waves.Audio circuitry 110 also receives electrical signals converted bymicrophone 113 from sound waves. Audio circuitry 110 converts theelectrical signal to audio data and transmits the audio data toperipherals interface 118 for processing. Audio data is, optionally,retrieved from and/or transmitted to memory 102 and/or RF circuitry 108by peripherals interface 118. In some embodiments, audio circuitry 110also includes a headset jack (e.g., 212, FIG. 2). The headset jackprovides an interface between audio circuitry 110 and removable audioinput/output peripherals, such as output-only headphones or a headsetwith both output (e.g., a headphone for one or both ears) and input(e.g., a microphone).

I/O subsystem 106 couples input/output peripherals on device 100, suchas touch screen 112 and other input control devices 116, to peripheralsinterface 118. I/O subsystem 106 optionally includes display controller156, optical sensor controller 158, depth camera controller 169,intensity sensor controller 159, haptic feedback controller 161, and oneor more input controllers 160 for other input or control devices. Theone or more input controllers 160 receive/send electrical signalsfrom/to other input control devices 116. The other input control devices116 optionally include physical buttons (e.g., push buttons, rockerbuttons, etc.), dials, slider switches, joysticks, click wheels, and soforth. In some embodiments, input controller(s) 160 are, optionally,coupled to any (or none) of the following: a keyboard, an infrared port,a USB port, and a pointer device such as a mouse. The one or morebuttons (e.g., 208, FIG. 2) optionally include an up/down button forvolume control of speaker 111 and/or microphone 113. The one or morebuttons optionally include a push button (e.g., 206, FIG. 2). In someembodiments, the electronic device is a computer system that is incommunication (e.g., via wireless communication, via wiredcommunication) with one or more input devices. In some embodiments, theone or more input devices include a touch-sensitive surface (e.g., atrackpad, as part of a touch-sensitive display). In some embodiments,the one or more input devices include one or more camera sensors (e.g.,one or more optical sensors 164 and/or one or more depth camera sensors175), such as for tracking a user's gestures (e.g., hand gestures) asinput. In some embodiments, the one or more input devices are integratedwith the computer system. In some embodiments, the one or more inputdevices are separate from the computer system.

A quick press of the push button optionally disengages a lock of touchscreen 112 or optionally begins a process that uses gestures on thetouch screen to unlock the device, as described in U.S. patentapplication Ser. No. 11/322,549, “Unlocking a Device by PerformingGestures on an Unlock Image,” filed Dec. 23, 2005, U.S. Pat. No.7,657,849, which is hereby incorporated by reference in its entirety. Alonger press of the push button (e.g., 206) optionally turns power todevice 100 on or off. The functionality of one or more of the buttonsare, optionally, user-customizable. Touch screen 112 is used toimplement virtual or soft buttons and one or more soft keyboards.

Touch-sensitive display 112 provides an input interface and an outputinterface between the device and a user. Display controller 156 receivesand/or sends electrical signals from/to touch screen 112. Touch screen112 displays visual output to the user. The visual output optionallyincludes graphics, text, icons, video, and any combination thereof(collectively termed “graphics”). In some embodiments, some or all ofthe visual output optionally corresponds to user-interface objects.

Touch screen 112 has a touch-sensitive surface, sensor, or set ofsensors that accepts input from the user based on haptic and/or tactilecontact. Touch screen 112 and display controller 156 (along with anyassociated modules and/or sets of instructions in memory 102) detectcontact (and any movement or breaking of the contact) on touch screen112 and convert the detected contact into interaction withuser-interface objects (e.g., one or more soft keys, icons, web pages,or images) that are displayed on touch screen 112. In an exemplaryembodiment, a point of contact between touch screen 112 and the usercorresponds to a finger of the user.

Touch screen 112 optionally uses LCD (liquid crystal display)technology, LPD (light emitting polymer display) technology, or LED(light emitting diode) technology, although other display technologiesare used in other embodiments. Touch screen 112 and display controller156 optionally detect contact and any movement or breaking thereof usingany of a plurality of touch sensing technologies now known or laterdeveloped, including but not limited to capacitive, resistive, infrared,and surface acoustic wave technologies, as well as other proximitysensor arrays or other elements for determining one or more points ofcontact with touch screen 112. In an exemplary embodiment, projectedmutual capacitance sensing technology is used, such as that found in theiPhone® and iPod Touch® from Apple Inc. of Cupertino, Calif.

A touch-sensitive display in some embodiments of touch screen 112 is,optionally, analogous to the multi-touch sensitive touchpads describedin the following U.S. Pat. No. 6,323,846 (Westerman et al.), U.S. Pat.No. 6,570,557 (Westerman et al.), and/or U.S. Pat. No. 6,677,932(Westerman), and/or U.S. Patent Publication 2002/0015024A1, each ofwhich is hereby incorporated by reference in its entirety. However,touch screen 112 displays visual output from device 100, whereastouch-sensitive touchpads do not provide visual output.

A touch-sensitive display in some embodiments of touch screen 112 isdescribed in the following applications: (1) U.S. patent applicationSer. No. 11/381,313, “Multipoint Touch Surface Controller,” filed May 2,2006; (2) U.S. patent application Ser. No. 10/840,862, “MultipointTouchscreen,” filed May 6, 2004; (3) U.S. patent application Ser. No.10/903,964, “Gestures For Touch Sensitive Input Devices,” filed Jul. 30,2004; (4) U.S. patent application Ser. No. 11/048,264, “Gestures ForTouch Sensitive Input Devices,” filed Jan. 31, 2005; (5) U.S. patentapplication Ser. No. 11/038,590, “Mode-Based Graphical User InterfacesFor Touch Sensitive Input Devices,” filed Jan. 18, 2005; (6) U.S. patentapplication Ser. No. 11/228,758, “Virtual Input Device Placement On ATouch Screen User Interface,” filed Sep. 16, 2005; (7) U.S. patentapplication Ser. No. 11/228,700, “Operation Of A Computer With A TouchScreen Interface,” filed Sep. 16, 2005; (8) U.S. patent application Ser.No. 11/228,737, “Activating Virtual Keys Of A Touch-Screen VirtualKeyboard,” filed Sep. 16, 2005; and (9) U.S. patent application Ser. No.11/367,749, “Multi-Functional Hand-Held Device,” filed Mar. 3, 2006. Allof these applications are incorporated by reference herein in theirentirety.

Touch screen 112 optionally has a video resolution in excess of 100 dpi.In some embodiments, the touch screen has a video resolution ofapproximately 160 dpi. The user optionally makes contact with touchscreen 112 using any suitable object or appendage, such as a stylus, afinger, and so forth. In some embodiments, the user interface isdesigned to work primarily with finger-based contacts and gestures,which can be less precise than stylus-based input due to the larger areaof contact of a finger on the touch screen. In some embodiments, thedevice translates the rough finger-based input into a precisepointer/cursor position or command for performing the actions desired bythe user.

In some embodiments, in addition to the touch screen, device 100optionally includes a touchpad for activating or deactivating particularfunctions. In some embodiments, the touchpad is a touch-sensitive areaof the device that, unlike the touch screen, does not display visualoutput. The touchpad is, optionally, a touch-sensitive surface that isseparate from touch screen 112 or an extension of the touch-sensitivesurface formed by the touch screen.

Device 100 also includes power system 162 for powering the variouscomponents. Power system 162 optionally includes a power managementsystem, one or more power sources (e.g., battery, alternating current(AC)), a recharging system, a power failure detection circuit, a powerconverter or inverter, a power status indicator (e.g., a light-emittingdiode (LED)) and any other components associated with the generation,management and distribution of power in portable devices.

Device 100 optionally also includes one or more optical sensors 164.FIG. 1A shows an optical sensor coupled to optical sensor controller 158in I/O subsystem 106. Optical sensor 164 optionally includescharge-coupled device (CCD) or complementary metal-oxide semiconductor(CMOS) phototransistors. Optical sensor 164 receives light from theenvironment, projected through one or more lenses, and converts thelight to data representing an image. In conjunction with imaging module143 (also called a camera module), optical sensor 164 optionallycaptures still images or video. In some embodiments, an optical sensoris located on the back of device 100, opposite touch screen display 112on the front of the device so that the touch screen display is enabledfor use as a viewfinder for still and/or video image acquisition. Insome embodiments, an optical sensor is located on the front of thedevice so that the user's image is, optionally, obtained for videoconferencing while the user views the other video conferenceparticipants on the touch screen display. In some embodiments, theposition of optical sensor 164 can be changed by the user (e.g., byrotating the lens and the sensor in the device housing) so that a singleoptical sensor 164 is used along with the touch screen display for bothvideo conferencing and still and/or video image acquisition.

Device 100 optionally also includes one or more depth camera sensors175. FIG. 1A shows a depth camera sensor coupled to depth cameracontroller 169 in I/O subsystem 106. Depth camera sensor 175 receivesdata from the environment to create a three dimensional model of anobject (e.g., a face) within a scene from a viewpoint (e.g., a depthcamera sensor). In some embodiments, in conjunction with imaging module143 (also called a camera module), depth camera sensor 175 is optionallyused to determine a depth map of different portions of an image capturedby the imaging module 143. In some embodiments, a depth camera sensor islocated on the front of device 100 so that the user's image with depthinformation is, optionally, obtained for video conferencing while theuser views the other video conference participants on the touch screendisplay and to capture selfies with depth map data. In some embodiments,the depth camera sensor 175 is located on the back of device, or on theback and the front of the device 100. In some embodiments, the positionof depth camera sensor 175 can be changed by the user (e.g., by rotatingthe lens and the sensor in the device housing) so that a depth camerasensor 175 is used along with the touch screen display for both videoconferencing and still and/or video image acquisition.

Device 100 optionally also includes one or more contact intensitysensors 165. FIG. 1A shows a contact intensity sensor coupled tointensity sensor controller 159 in I/O subsystem 106. Contact intensitysensor 165 optionally includes one or more piezoresistive strain gauges,capacitive force sensors, electric force sensors, piezoelectric forcesensors, optical force sensors, capacitive touch-sensitive surfaces, orother intensity sensors (e.g., sensors used to measure the force (orpressure) of a contact on a touch-sensitive surface). Contact intensitysensor 165 receives contact intensity information (e.g., pressureinformation or a proxy for pressure information) from the environment.In some embodiments, at least one contact intensity sensor is collocatedwith, or proximate to, a touch-sensitive surface (e.g., touch-sensitivedisplay system 112). In some embodiments, at least one contact intensitysensor is located on the back of device 100, opposite touch screendisplay 112, which is located on the front of device 100.

Device 100 optionally also includes one or more proximity sensors 166.FIG. 1A shows proximity sensor 166 coupled to peripherals interface 118.Alternately, proximity sensor 166 is, optionally, coupled to inputcontroller 160 in I/O subsystem 106. Proximity sensor 166 optionallyperforms as described in U.S. patent application Ser. No. 11/241,839,“Proximity Detector In Handheld Device”; Ser. No. 11/240,788, “ProximityDetector In Handheld Device”; Ser. No. 11/620,702, “Using Ambient LightSensor To Augment Proximity Sensor Output”; Ser. No. 11/586,862,“Automated Response To And Sensing Of User Activity In PortableDevices”; and Ser. No. 11/638,251, “Methods And Systems For AutomaticConfiguration Of Peripherals,” which are hereby incorporated byreference in their entirety. In some embodiments, the proximity sensorturns off and disables touch screen 112 when the multifunction device isplaced near the user's ear (e.g., when the user is making a phone call).

Device 100 optionally also includes one or more tactile outputgenerators 167. FIG. 1A shows a tactile output generator coupled tohaptic feedback controller 161 in I/O subsystem 106. Tactile outputgenerator 167 optionally includes one or more electroacoustic devicessuch as speakers or other audio components and/or electromechanicaldevices that convert energy into linear motion such as a motor,solenoid, electroactive polymer, piezoelectric actuator, electrostaticactuator, or other tactile output generating component (e.g., acomponent that converts electrical signals into tactile outputs on thedevice). Contact intensity sensor 165 receives tactile feedbackgeneration instructions from haptic feedback module 133 and generatestactile outputs on device 100 that are capable of being sensed by a userof device 100. In some embodiments, at least one tactile outputgenerator is collocated with, or proximate to, a touch-sensitive surface(e.g., touch-sensitive display system 112) and, optionally, generates atactile output by moving the touch-sensitive surface vertically (e.g.,in/out of a surface of device 100) or laterally (e.g., back and forth inthe same plane as a surface of device 100). In some embodiments, atleast one tactile output generator sensor is located on the back ofdevice 100, opposite touch screen display 112, which is located on thefront of device 100.

Device 100 optionally also includes one or more accelerometers 168. FIG.1A shows accelerometer 168 coupled to peripherals interface 118.Alternately, accelerometer 168 is, optionally, coupled to an inputcontroller 160 in I/O subsystem 106. Accelerometer 168 optionallyperforms as described in U.S. Patent Publication No. 20050190059,“Acceleration-based Theft Detection System for Portable ElectronicDevices,” and U.S. Patent Publication No. 20060017692, “Methods AndApparatuses For Operating A Portable Device Based On An Accelerometer,”both of which are incorporated by reference herein in their entirety. Insome embodiments, information is displayed on the touch screen displayin a portrait view or a landscape view based on an analysis of datareceived from the one or more accelerometers. Device 100 optionallyincludes, in addition to accelerometer(s) 168, a magnetometer and a GPS(or GLONASS or other global navigation system) receiver for obtaininginformation concerning the location and orientation (e.g., portrait orlandscape) of device 100.

In some embodiments, the software components stored in memory 102include operating system 126, communication module (or set ofinstructions) 128, contact/motion module (or set of instructions) 130,graphics module (or set of instructions) 132, text input module (or setof instructions) 134, Global Positioning System (GPS) module (or set ofinstructions) 135, and applications (or sets of instructions) 136.Furthermore, in some embodiments, memory 102 (FIG. 1A) or 370 (FIG. 3)stores device/global internal state 157, as shown in FIGS. 1A and 3.Device/global internal state 157 includes one or more of: activeapplication state, indicating which applications, if any, are currentlyactive; display state, indicating what applications, views or otherinformation occupy various regions of touch screen display 112; sensorstate, including information obtained from the device's various sensorsand input control devices 116; and location information concerning thedevice's location and/or attitude.

Operating system 126 (e.g., Darwin, RTXC, LINUX, UNIX, OS X, iOS,WINDOWS, or an embedded operating system such as VxWorks) includesvarious software components and/or drivers for controlling and managinggeneral system tasks (e.g., memory management, storage device control,power management, etc.) and facilitates communication between varioushardware and software components.

Communication module 128 facilitates communication with other devicesover one or more external ports 124 and also includes various softwarecomponents for handling data received by RF circuitry 108 and/orexternal port 124. External port 124 (e.g., Universal Serial Bus (USB),FIREWIRE, etc.) is adapted for coupling directly to other devices orindirectly over a network (e.g., the Internet, wireless LAN, etc.). Insome embodiments, the external port is a multi-pin (e.g., 30-pin)connector that is the same as, or similar to and/or compatible with, the30-pin connector used on iPod® (trademark of Apple Inc.) devices.

Contact/motion module 130 optionally detects contact with touch screen112 (in conjunction with display controller 156) and othertouch-sensitive devices (e.g., a touchpad or physical click wheel).Contact/motion module 130 includes various software components forperforming various operations related to detection of contact, such asdetermining if contact has occurred (e.g., detecting a finger-downevent), determining an intensity of the contact (e.g., the force orpressure of the contact or a substitute for the force or pressure of thecontact), determining if there is movement of the contact and trackingthe movement across the touch-sensitive surface (e.g., detecting one ormore finger-dragging events), and determining if the contact has ceased(e.g., detecting a finger-up event or a break in contact).Contact/motion module 130 receives contact data from the touch-sensitivesurface. Determining movement of the point of contact, which isrepresented by a series of contact data, optionally includes determiningspeed (magnitude), velocity (magnitude and direction), and/or anacceleration (a change in magnitude and/or direction) of the point ofcontact. These operations are, optionally, applied to single contacts(e.g., one finger contacts) or to multiple simultaneous contacts (e.g.,“multitouch”/multiple finger contacts). In some embodiments,contact/motion module 130 and display controller 156 detect contact on atouchpad.

In some embodiments, contact/motion module 130 uses a set of one or moreintensity thresholds to determine whether an operation has beenperformed by a user (e.g., to determine whether a user has “clicked” onan icon). In some embodiments, at least a subset of the intensitythresholds are determined in accordance with software parameters (e.g.,the intensity thresholds are not determined by the activation thresholdsof particular physical actuators and can be adjusted without changingthe physical hardware of device 100). For example, a mouse “click”threshold of a trackpad or touch screen display can be set to any of alarge range of predefined threshold values without changing the trackpador touch screen display hardware. Additionally, in some implementations,a user of the device is provided with software settings for adjustingone or more of the set of intensity thresholds (e.g., by adjustingindividual intensity thresholds and/or by adjusting a plurality ofintensity thresholds at once with a system-level click “intensity”parameter).

Contact/motion module 130 optionally detects a gesture input by a user.Different gestures on the touch-sensitive surface have different contactpatterns (e.g., different motions, timings, and/or intensities ofdetected contacts). Thus, a gesture is, optionally, detected bydetecting a particular contact pattern. For example, detecting a fingertap gesture includes detecting a finger-down event followed by detectinga finger-up (liftoff) event at the same position (or substantially thesame position) as the finger-down event (e.g., at the position of anicon). As another example, detecting a finger swipe gesture on thetouch-sensitive surface includes detecting a finger-down event followedby detecting one or more finger-dragging events, and subsequentlyfollowed by detecting a finger-up (liftoff) event.

Graphics module 132 includes various known software components forrendering and displaying graphics on touch screen 112 or other display,including components for changing the visual impact (e.g., brightness,transparency, saturation, contrast, or other visual property) ofgraphics that are displayed. As used herein, the term “graphics”includes any object that can be displayed to a user, including, withoutlimitation, text, web pages, icons (such as user-interface objectsincluding soft keys), digital images, videos, animations, and the like.

In some embodiments, graphics module 132 stores data representinggraphics to be used. Each graphic is, optionally, assigned acorresponding code. Graphics module 132 receives, from applicationsetc., one or more codes specifying graphics to be displayed along with,if necessary, coordinate data and other graphic property data, and thengenerates screen image data to output to display controller 156.

Haptic feedback module 133 includes various software components forgenerating instructions used by tactile output generator(s) 167 toproduce tactile outputs at one or more locations on device 100 inresponse to user interactions with device 100.

Text input module 134, which is, optionally, a component of graphicsmodule 132, provides soft keyboards for entering text in variousapplications (e.g., contacts 137, e-mail 140, IM 141, browser 147, andany other application that needs text input).

GPS module 135 determines the location of the device and provides thisinformation for use in various applications (e.g., to telephone 138 foruse in location-based dialing; to camera 143 as picture/video metadata;and to applications that provide location-based services such as weatherwidgets, local yellow page widgets, and map/navigation widgets).

Applications 136 optionally include the following modules (or sets ofinstructions), or a subset or superset thereof:

-   -   Contacts module 137 (sometimes called an address book or contact        list);    -   Telephone module 138;    -   Video conference module 139;    -   E-mail client module 140;    -   Instant messaging (IM) module 141;    -   Workout support module 142;    -   Camera module 143 for still and/or video images;    -   Image management module 144;    -   Video player module;    -   Music player module;    -   Browser module 147;    -   Calendar module 148;    -   Widget modules 149, which optionally include one or more of:        weather widget 149-1, stocks widget 149-2, calculator widget        149-3, alarm clock widget 149-4, dictionary widget 149-5, and        other widgets obtained by the user, as well as user-created        widgets 149-6;    -   Widget creator module 150 for making user-created widgets 149-6;    -   Search module 151;    -   Video and music player module 152, which merges video player        module and music player module;    -   Notes module 153;    -   Map module 154; and/or    -   Online video module 155.

Examples of other applications 136 that are, optionally, stored inmemory 102 include other word processing applications, other imageediting applications, drawing applications, presentation applications,JAVA-enabled applications, encryption, digital rights management, voicerecognition, and voice replication.

In conjunction with touch screen 112, display controller 156,contact/motion module 130, graphics module 132, and text input module134, contacts module 137 are, optionally, used to manage an address bookor contact list (e.g., stored in application internal state 192 ofcontacts module 137 in memory 102 or memory 370), including: addingname(s) to the address book; deleting name(s) from the address book;associating telephone number(s), e-mail address(es), physicaladdress(es) or other information with a name; associating an image witha name; categorizing and sorting names; providing telephone numbers ore-mail addresses to initiate and/or facilitate communications bytelephone 138, video conference module 139, e-mail 140, or IM 141; andso forth.

In conjunction with RF circuitry 108, audio circuitry 110, speaker 111,microphone 113, touch screen 112, display controller 156, contact/motionmodule 130, graphics module 132, and text input module 134, telephonemodule 138 are optionally, used to enter a sequence of characterscorresponding to a telephone number, access one or more telephonenumbers in contacts module 137, modify a telephone number that has beenentered, dial a respective telephone number, conduct a conversation, anddisconnect or hang up when the conversation is completed. As notedabove, the wireless communication optionally uses any of a plurality ofcommunications standards, protocols, and technologies.

In conjunction with RF circuitry 108, audio circuitry 110, speaker 111,microphone 113, touch screen 112, display controller 156, optical sensor164, optical sensor controller 158, contact/motion module 130, graphicsmodule 132, text input module 134, contacts module 137, and telephonemodule 138, video conference module 139 includes executable instructionsto initiate, conduct, and terminate a video conference between a userand one or more other participants in accordance with user instructions.

In conjunction with RF circuitry 108, touch screen 112, displaycontroller 156, contact/motion module 130, graphics module 132, and textinput module 134, e-mail client module 140 includes executableinstructions to create, send, receive, and manage e-mail in response touser instructions. In conjunction with image management module 144,e-mail client module 140 makes it very easy to create and send e-mailswith still or video images taken with camera module 143.

In conjunction with RF circuitry 108, touch screen 112, displaycontroller 156, contact/motion module 130, graphics module 132, and textinput module 134, the instant messaging module 141 includes executableinstructions to enter a sequence of characters corresponding to aninstant message, to modify previously entered characters, to transmit arespective instant message (for example, using a Short Message Service(SMS) or Multimedia Message Service (MMS) protocol for telephony-basedinstant messages or using XMPP, SIMPLE, or IMPS for Internet-basedinstant messages), to receive instant messages, and to view receivedinstant messages. In some embodiments, transmitted and/or receivedinstant messages optionally include graphics, photos, audio files, videofiles and/or other attachments as are supported in an MMS and/or anEnhanced Messaging Service (EMS). As used herein, “instant messaging”refers to both telephony-based messages (e.g., messages sent using SMSor MMS) and Internet-based messages (e.g., messages sent using XMPP,SIMPLE, or IMPS).

In conjunction with RF circuitry 108, touch screen 112, displaycontroller 156, contact/motion module 130, graphics module 132, textinput module 134, GPS module 135, map module 154, and music playermodule, workout support module 142 includes executable instructions tocreate workouts (e.g., with time, distance, and/or calorie burninggoals); communicate with workout sensors (sports devices); receiveworkout sensor data; calibrate sensors used to monitor a workout; selectand play music for a workout; and display, store, and transmit workoutdata.

In conjunction with touch screen 112, display controller 156, opticalsensor(s) 164, optical sensor controller 158, contact/motion module 130,graphics module 132, and image management module 144, camera module 143includes executable instructions to capture still images or video(including a video stream) and store them into memory 102, modifycharacteristics of a still image or video, or delete a still image orvideo from memory 102.

In conjunction with touch screen 112, display controller 156,contact/motion module 130, graphics module 132, text input module 134,and camera module 143, image management module 144 includes executableinstructions to arrange, modify (e.g., edit), or otherwise manipulate,label, delete, present (e.g., in a digital slide show or album), andstore still and/or video images.

In conjunction with RF circuitry 108, touch screen 112, displaycontroller 156, contact/motion module 130, graphics module 132, and textinput module 134, browser module 147 includes executable instructions tobrowse the Internet in accordance with user instructions, includingsearching, linking to, receiving, and displaying web pages or portionsthereof, as well as attachments and other files linked to web pages.

In conjunction with RF circuitry 108, touch screen 112, displaycontroller 156, contact/motion module 130, graphics module 132, textinput module 134, e-mail client module 140, and browser module 147,calendar module 148 includes executable instructions to create, display,modify, and store calendars and data associated with calendars (e.g.,calendar entries, to-do lists, etc.) in accordance with userinstructions.

In conjunction with RF circuitry 108, touch screen 112, displaycontroller 156, contact/motion module 130, graphics module 132, textinput module 134, and browser module 147, widget modules 149 aremini-applications that are, optionally, downloaded and used by a user(e.g., weather widget 149-1, stocks widget 149-2, calculator widget149-3, alarm clock widget 149-4, and dictionary widget 149-5) or createdby the user (e.g., user-created widget 149-6). In some embodiments, awidget includes an HTML (Hypertext Markup Language) file, a CSS(Cascading Style Sheets) file, and a JavaScript file. In someembodiments, a widget includes an XML (Extensible Markup Language) fileand a JavaScript file (e.g., Yahoo! Widgets).

In conjunction with RF circuitry 108, touch screen 112, displaycontroller 156, contact/motion module 130, graphics module 132, textinput module 134, and browser module 147, the widget creator module 150are, optionally, used by a user to create widgets (e.g., turning auser-specified portion of a web page into a widget).

In conjunction with touch screen 112, display controller 156,contact/motion module 130, graphics module 132, and text input module134, search module 151 includes executable instructions to search fortext, music, sound, image, video, and/or other files in memory 102 thatmatch one or more search criteria (e.g., one or more user-specifiedsearch terms) in accordance with user instructions.

In conjunction with touch screen 112, display controller 156,contact/motion module 130, graphics module 132, audio circuitry 110,speaker 111, RF circuitry 108, and browser module 147, video and musicplayer module 152 includes executable instructions that allow the userto download and play back recorded music and other sound files stored inone or more file formats, such as MP3 or AAC files, and executableinstructions to display, present, or otherwise play back videos (e.g.,on touch screen 112 or on an external, connected display via externalport 124). In some embodiments, device 100 optionally includes thefunctionality of an MP3 player, such as an iPod (trademark of AppleInc.).

In conjunction with touch screen 112, display controller 156,contact/motion module 130, graphics module 132, and text input module134, notes module 153 includes executable instructions to create andmanage notes, to-do lists, and the like in accordance with userinstructions.

In conjunction with RF circuitry 108, touch screen 112, displaycontroller 156, contact/motion module 130, graphics module 132, textinput module 134, GPS module 135, and browser module 147, map module 154are, optionally, used to receive, display, modify, and store maps anddata associated with maps (e.g., driving directions, data on stores andother points of interest at or near a particular location, and otherlocation-based data) in accordance with user instructions.

In conjunction with touch screen 112, display controller 156,contact/motion module 130, graphics module 132, audio circuitry 110,speaker 111, RF circuitry 108, text input module 134, e-mail clientmodule 140, and browser module 147, online video module 155 includesinstructions that allow the user to access, browse, receive (e.g., bystreaming and/or download), play back (e.g., on the touch screen or onan external, connected display via external port 124), send an e-mailwith a link to a particular online video, and otherwise manage onlinevideos in one or more file formats, such as H.264. In some embodiments,instant messaging module 141, rather than e-mail client module 140, isused to send a link to a particular online video. Additional descriptionof the online video application can be found in U.S. Provisional PatentApplication No. 60/936,562, “Portable Multifunction Device, Method, andGraphical User Interface for Playing Online Videos,” filed Jun. 20,2007, and U.S. patent application Ser. No. 11/968,067, “PortableMultifunction Device, Method, and Graphical User Interface for PlayingOnline Videos,” filed Dec. 31, 2007, the contents of which are herebyincorporated by reference in their entirety.

Each of the above-identified modules and applications corresponds to aset of executable instructions for performing one or more functionsdescribed above and the methods described in this application (e.g., thecomputer-implemented methods and other information processing methodsdescribed herein). These modules (e.g., sets of instructions) need notbe implemented as separate software programs, procedures, or modules,and thus various subsets of these modules are, optionally, combined orotherwise rearranged in various embodiments. For example, video playermodule is, optionally, combined with music player module into a singlemodule (e.g., video and music player module 152, FIG. 1A). In someembodiments, memory 102 optionally stores a subset of the modules anddata structures identified above. Furthermore, memory 102 optionallystores additional modules and data structures not described above.

In some embodiments, device 100 is a device where operation of apredefined set of functions on the device is performed exclusivelythrough a touch screen and/or a touchpad. By using a touch screen and/ora touchpad as the primary input control device for operation of device100, the number of physical input control devices (such as push buttons,dials, and the like) on device 100 is, optionally, reduced.

The predefined set of functions that are performed exclusively through atouch screen and/or a touchpad optionally include navigation betweenuser interfaces. In some embodiments, the touchpad, when touched by theuser, navigates device 100 to a main, home, or root menu from any userinterface that is displayed on device 100. In such embodiments, a “menubutton” is implemented using a touchpad. In some other embodiments, themenu button is a physical push button or other physical input controldevice instead of a touchpad.

FIG. 1B is a block diagram illustrating exemplary components for eventhandling in accordance with some embodiments. In some embodiments,memory 102 (FIG. 1A) or 370 (FIG. 3) includes event sorter 170 (e.g., inoperating system 126) and a respective application 136-1 (e.g., any ofthe aforementioned applications 137-151, 155, 380-390).

Event sorter 170 receives event information and determines theapplication 136-1 and application view 191 of application 136-1 to whichto deliver the event information. Event sorter 170 includes eventmonitor 171 and event dispatcher module 174. In some embodiments,application 136-1 includes application internal state 192, whichindicates the current application view(s) displayed on touch-sensitivedisplay 112 when the application is active or executing. In someembodiments, device/global internal state 157 is used by event sorter170 to determine which application(s) is (are) currently active, andapplication internal state 192 is used by event sorter 170 to determineapplication views 191 to which to deliver event information.

In some embodiments, application internal state 192 includes additionalinformation, such as one or more of: resume information to be used whenapplication 136-1 resumes execution, user interface state informationthat indicates information being displayed or that is ready for displayby application 136-1, a state queue for enabling the user to go back toa prior state or view of application 136-1, and a redo/undo queue ofprevious actions taken by the user.

Event monitor 171 receives event information from peripherals interface118. Event information includes information about a sub-event (e.g., auser touch on touch-sensitive display 112, as part of a multi-touchgesture). Peripherals interface 118 transmits information it receivesfrom I/O subsystem 106 or a sensor, such as proximity sensor 166,accelerometer(s) 168, and/or microphone 113 (through audio circuitry110). Information that peripherals interface 118 receives from I/Osubsystem 106 includes information from touch-sensitive display 112 or atouch-sensitive surface.

In some embodiments, event monitor 171 sends requests to the peripheralsinterface 118 at predetermined intervals. In response, peripheralsinterface 118 transmits event information. In other embodiments,peripherals interface 118 transmits event information only when there isa significant event (e.g., receiving an input above a predeterminednoise threshold and/or for more than a predetermined duration).

In some embodiments, event sorter 170 also includes a hit viewdetermination module 172 and/or an active event recognizer determinationmodule 173.

Hit view determination module 172 provides software procedures fordetermining where a sub-event has taken place within one or more viewswhen touch-sensitive display 112 displays more than one view. Views aremade up of controls and other elements that a user can see on thedisplay.

Another aspect of the user interface associated with an application is aset of views, sometimes herein called application views or userinterface windows, in which information is displayed and touch-basedgestures occur. The application views (of a respective application) inwhich a touch is detected optionally correspond to programmatic levelswithin a programmatic or view hierarchy of the application. For example,the lowest level view in which a touch is detected is, optionally,called the hit view, and the set of events that are recognized as properinputs are, optionally, determined based, at least in part, on the hitview of the initial touch that begins a touch-based gesture.

Hit view determination module 172 receives information related tosub-events of a touch-based gesture. When an application has multipleviews organized in a hierarchy, hit view determination module 172identifies a hit view as the lowest view in the hierarchy which shouldhandle the sub-event. In most circumstances, the hit view is the lowestlevel view in which an initiating sub-event occurs (e.g., the firstsub-event in the sequence of sub-events that form an event or potentialevent). Once the hit view is identified by the hit view determinationmodule 172, the hit view typically receives all sub-events related tothe same touch or input source for which it was identified as the hitview.

Active event recognizer determination module 173 determines which viewor views within a view hierarchy should receive a particular sequence ofsub-events. In some embodiments, active event recognizer determinationmodule 173 determines that only the hit view should receive a particularsequence of sub-events. In other embodiments, active event recognizerdetermination module 173 determines that all views that include thephysical location of a sub-event are actively involved views, andtherefore determines that all actively involved views should receive aparticular sequence of sub-events. In other embodiments, even if touchsub-events were entirely confined to the area associated with oneparticular view, views higher in the hierarchy would still remain asactively involved views.

Event dispatcher module 174 dispatches the event information to an eventrecognizer (e.g., event recognizer 180). In embodiments including activeevent recognizer determination module 173, event dispatcher module 174delivers the event information to an event recognizer determined byactive event recognizer determination module 173. In some embodiments,event dispatcher module 174 stores in an event queue the eventinformation, which is retrieved by a respective event receiver 182.

In some embodiments, operating system 126 includes event sorter 170.Alternatively, application 136-1 includes event sorter 170. In yet otherembodiments, event sorter 170 is a stand-alone module, or a part ofanother module stored in memory 102, such as contact/motion module 130.

In some embodiments, application 136-1 includes a plurality of eventhandlers 190 and one or more application views 191, each of whichincludes instructions for handling touch events that occur within arespective view of the application's user interface. Each applicationview 191 of the application 136-1 includes one or more event recognizers180. Typically, a respective application view 191 includes a pluralityof event recognizers 180. In other embodiments, one or more of eventrecognizers 180 are part of a separate module, such as a user interfacekit or a higher level object from which application 136-1 inheritsmethods and other properties. In some embodiments, a respective eventhandler 190 includes one or more of: data updater 176, object updater177, GUI updater 178, and/or event data 179 received from event sorter170. Event handler 190 optionally utilizes or calls data updater 176,object updater 177, or GUI updater 178 to update the applicationinternal state 192. Alternatively, one or more of the application views191 include one or more respective event handlers 190. Also, in someembodiments, one or more of data updater 176, object updater 177, andGUI updater 178 are included in a respective application view 191.

A respective event recognizer 180 receives event information (e.g.,event data 179) from event sorter 170 and identifies an event from theevent information. Event recognizer 180 includes event receiver 182 andevent comparator 184. In some embodiments, event recognizer 180 alsoincludes at least a subset of: metadata 183, and event deliveryinstructions 188 (which optionally include sub-event deliveryinstructions).

Event receiver 182 receives event information from event sorter 170. Theevent information includes information about a sub-event, for example, atouch or a touch movement. Depending on the sub-event, the eventinformation also includes additional information, such as location ofthe sub-event. When the sub-event concerns motion of a touch, the eventinformation optionally also includes speed and direction of thesub-event. In some embodiments, events include rotation of the devicefrom one orientation to another (e.g., from a portrait orientation to alandscape orientation, or vice versa), and the event informationincludes corresponding information about the current orientation (alsocalled device attitude) of the device.

Event comparator 184 compares the event information to predefined eventor sub-event definitions and, based on the comparison, determines anevent or sub-event, or determines or updates the state of an event orsub-event. In some embodiments, event comparator 184 includes eventdefinitions 186. Event definitions 186 contain definitions of events(e.g., predefined sequences of sub-events), for example, event 1(187-1), event 2 (187-2), and others. In some embodiments, sub-events inan event (187) include, for example, touch begin, touch end, touchmovement, touch cancellation, and multiple touching. In one example, thedefinition for event 1 (187-1) is a double tap on a displayed object.The double tap, for example, comprises a first touch (touch begin) onthe displayed object for a predetermined phase, a first liftoff (touchend) for a predetermined phase, a second touch (touch begin) on thedisplayed object for a predetermined phase, and a second liftoff (touchend) for a predetermined phase. In another example, the definition forevent 2 (187-2) is a dragging on a displayed object. The dragging, forexample, comprises a touch (or contact) on the displayed object for apredetermined phase, a movement of the touch across touch-sensitivedisplay 112, and liftoff of the touch (touch end). In some embodiments,the event also includes information for one or more associated eventhandlers 190.

In some embodiments, event definition 187 includes a definition of anevent for a respective user-interface object. In some embodiments, eventcomparator 184 performs a hit test to determine which user-interfaceobject is associated with a sub-event. For example, in an applicationview in which three user-interface objects are displayed ontouch-sensitive display 112, when a touch is detected on touch-sensitivedisplay 112, event comparator 184 performs a hit test to determine whichof the three user-interface objects is associated with the touch(sub-event). If each displayed object is associated with a respectiveevent handler 190, the event comparator uses the result of the hit testto determine which event handler 190 should be activated. For example,event comparator 184 selects an event handler associated with thesub-event and the object triggering the hit test.

In some embodiments, the definition for a respective event (187) alsoincludes delayed actions that delay delivery of the event informationuntil after it has been determined whether the sequence of sub-eventsdoes or does not correspond to the event recognizer's event type.

When a respective event recognizer 180 determines that the series ofsub-events do not match any of the events in event definitions 186, therespective event recognizer 180 enters an event impossible, eventfailed, or event ended state, after which it disregards subsequentsub-events of the touch-based gesture. In this situation, other eventrecognizers, if any, that remain active for the hit view continue totrack and process sub-events of an ongoing touch-based gesture.

In some embodiments, a respective event recognizer 180 includes metadata183 with configurable properties, flags, and/or lists that indicate howthe event delivery system should perform sub-event delivery to activelyinvolved event recognizers. In some embodiments, metadata 183 includesconfigurable properties, flags, and/or lists that indicate how eventrecognizers interact, or are enabled to interact, with one another. Insome embodiments, metadata 183 includes configurable properties, flags,and/or lists that indicate whether sub-events are delivered to varyinglevels in the view or programmatic hierarchy.

In some embodiments, a respective event recognizer 180 activates eventhandler 190 associated with an event when one or more particularsub-events of an event are recognized. In some embodiments, a respectiveevent recognizer 180 delivers event information associated with theevent to event handler 190. Activating an event handler 190 is distinctfrom sending (and deferred sending) sub-events to a respective hit view.In some embodiments, event recognizer 180 throws a flag associated withthe recognized event, and event handler 190 associated with the flagcatches the flag and performs a predefined process.

In some embodiments, event delivery instructions 188 include sub-eventdelivery instructions that deliver event information about a sub-eventwithout activating an event handler. Instead, the sub-event deliveryinstructions deliver event information to event handlers associated withthe series of sub-events or to actively involved views. Event handlersassociated with the series of sub-events or with actively involved viewsreceive the event information and perform a predetermined process.

In some embodiments, data updater 176 creates and updates data used inapplication 136-1. For example, data updater 176 updates the telephonenumber used in contacts module 137, or stores a video file used in videoplayer module. In some embodiments, object updater 177 creates andupdates objects used in application 136-1. For example, object updater177 creates a new user-interface object or updates the position of auser-interface object. GUI updater 178 updates the GUI. For example, GUIupdater 178 prepares display information and sends it to graphics module132 for display on a touch-sensitive display.

In some embodiments, event handler(s) 190 includes or has access to dataupdater 176, object updater 177, and GUI updater 178. In someembodiments, data updater 176, object updater 177, and GUI updater 178are included in a single module of a respective application 136-1 orapplication view 191. In other embodiments, they are included in two ormore software modules.

It shall be understood that the foregoing discussion regarding eventhandling of user touches on touch-sensitive displays also applies toother forms of user inputs to operate multifunction devices 100 withinput devices, not all of which are initiated on touch screens. Forexample, mouse movement and mouse button presses, optionally coordinatedwith single or multiple keyboard presses or holds; contact movementssuch as taps, drags, scrolls, etc. on touchpads; pen stylus inputs;movement of the device; oral instructions; detected eye movements;biometric inputs; and/or any combination thereof are optionally utilizedas inputs corresponding to sub-events which define an event to berecognized.

FIG. 2 illustrates a portable multifunction device 100 having a touchscreen 112 in accordance with some embodiments. The touch screenoptionally displays one or more graphics within user interface (UI) 200.In this embodiment, as well as others described below, a user is enabledto select one or more of the graphics by making a gesture on thegraphics, for example, with one or more fingers 202 (not drawn to scalein the figure) or one or more styluses 203 (not drawn to scale in thefigure). In some embodiments, selection of one or more graphics occurswhen the user breaks contact with the one or more graphics. In someembodiments, the gesture optionally includes one or more taps, one ormore swipes (from left to right, right to left, upward and/or downward),and/or a rolling of a finger (from right to left, left to right, upwardand/or downward) that has made contact with device 100. In someimplementations or circumstances, inadvertent contact with a graphicdoes not select the graphic. For example, a swipe gesture that sweepsover an application icon optionally does not select the correspondingapplication when the gesture corresponding to selection is a tap.

Device 100 optionally also include one or more physical buttons, such as“home” or menu button 204. As described previously, menu button 204 is,optionally, used to navigate to any application 136 in a set ofapplications that are, optionally, executed on device 100.Alternatively, in some embodiments, the menu button is implemented as asoft key in a GUI displayed on touch screen 112.

In some embodiments, device 100 includes touch screen 112, menu button204, push button 206 for powering the device on/off and locking thedevice, volume adjustment button(s) 208, subscriber identity module(SIM) card slot 210, headset jack 212, and docking/charging externalport 124. Push button 206 is, optionally, used to turn the power on/offon the device by depressing the button and holding the button in thedepressed state for a predefined time interval; to lock the device bydepressing the button and releasing the button before the predefinedtime interval has elapsed; and/or to unlock the device or initiate anunlock process. In an alternative embodiment, device 100 also acceptsverbal input for activation or deactivation of some functions throughmicrophone 113. Device 100 also, optionally, includes one or morecontact intensity sensors 165 for detecting intensity of contacts ontouch screen 112 and/or one or more tactile output generators 167 forgenerating tactile outputs for a user of device 100.

FIG. 3 is a block diagram of an exemplary multifunction device with adisplay and a touch-sensitive surface in accordance with someembodiments. Device 300 need not be portable. In some embodiments,device 300 is a laptop computer, a desktop computer, a tablet computer,a multimedia player device, a navigation device, an educational device(such as a child's learning toy), a gaming system, or a control device(e.g., a home or industrial controller). Device 300 typically includesone or more processing units (CPUs) 310, one or more network or othercommunications interfaces 360, memory 370, and one or more communicationbuses 320 for interconnecting these components. Communication buses 320optionally include circuitry (sometimes called a chipset) thatinterconnects and controls communications between system components.Device 300 includes input/output (I/O) interface 330 comprising display340, which is typically a touch screen display. I/O interface 330 alsooptionally includes a keyboard and/or mouse (or other pointing device)350 and touchpad 355, tactile output generator 357 for generatingtactile outputs on device 300 (e.g., similar to tactile outputgenerator(s) 167 described above with reference to FIG. 1A), sensors 359(e.g., optical, acceleration, proximity, touch-sensitive, and/or contactintensity sensors similar to contact intensity sensor(s) 165 describedabove with reference to FIG. 1A). Memory 370 includes high-speed randomaccess memory, such as DRAM, SRAM, DDR RAM, or other random access solidstate memory devices; and optionally includes non-volatile memory, suchas one or more magnetic disk storage devices, optical disk storagedevices, flash memory devices, or other non-volatile solid state storagedevices. Memory 370 optionally includes one or more storage devicesremotely located from CPU(s) 310. In some embodiments, memory 370 storesprograms, modules, and data structures analogous to the programs,modules, and data structures stored in memory 102 of portablemultifunction device 100 (FIG. 1A), or a subset thereof. Furthermore,memory 370 optionally stores additional programs, modules, and datastructures not present in memory 102 of portable multifunction device100. For example, memory 370 of device 300 optionally stores drawingmodule 380, presentation module 382, word processing module 384, websitecreation module 386, disk authoring module 388, and/or spreadsheetmodule 390, while memory 102 of portable multifunction device 100 (FIG.1A) optionally does not store these modules.

Each of the above-identified elements in FIG. 3 is, optionally, storedin one or more of the previously mentioned memory devices. Each of theabove-identified modules corresponds to a set of instructions forperforming a function described above. The above-identified modules orprograms (e.g., sets of instructions) need not be implemented asseparate software programs, procedures, or modules, and thus varioussubsets of these modules are, optionally, combined or otherwiserearranged in various embodiments. In some embodiments, memory 370optionally stores a subset of the modules and data structures identifiedabove. Furthermore, memory 370 optionally stores additional modules anddata structures not described above.

Attention is now directed towards embodiments of user interfaces thatare, optionally, implemented on, for example, portable multifunctiondevice 100.

FIG. 4A illustrates an exemplary user interface for a menu ofapplications on portable multifunction device 100 in accordance withsome embodiments. Similar user interfaces are, optionally, implementedon device 300. In some embodiments, user interface 400 includes thefollowing elements, or a subset or superset thereof:

-   -   Signal strength indicator(s) 402 for wireless communication(s),        such as cellular and Wi-Fi signals;    -   Time 404;    -   Bluetooth indicator 405;    -   Battery status indicator 406;    -   Tray 408 with icons for frequently used applications, such as:        -   Icon 416 for telephone module 138, labeled “Phone,” which            optionally includes an indicator 414 of the number of missed            calls or voicemail messages;        -   Icon 418 for e-mail client module 140, labeled “Mail,” which            optionally includes an indicator 410 of the number of unread            e-mails;        -   Icon 420 for browser module 147, labeled “Browser;” and        -   Icon 422 for video and music player module 152, also            referred to as iPod (trademark of Apple Inc.) module 152,            labeled “iPod;” and    -   Icons for other applications, such as:        -   Icon 424 for IM module 141, labeled “Messages;”        -   Icon 426 for calendar module 148, labeled “Calendar;”        -   Icon 428 for image management module 144, labeled “Photos;”        -   Icon 430 for camera module 143, labeled “Camera;”        -   Icon 432 for online video module 155, labeled “Online            Video;”        -   Icon 434 for stocks widget 149-2, labeled “Stocks;”        -   Icon 436 for map module 154, labeled “Maps;”        -   Icon 438 for weather widget 149-1, labeled “Weather;”        -   Icon 440 for alarm clock widget 149-4, labeled “Clock;”        -   Icon 442 for workout support module 142, labeled “Workout            Support;”        -   Icon 444 for notes module 153, labeled “Notes;” and        -   Icon 446 for a settings application or module, labeled            “Settings,” which provides access to settings for device 100            and its various applications 136.

It should be noted that the icon labels illustrated in FIG. 4A aremerely exemplary. For example, icon 422 for video and music playermodule 152 is labeled “Music” or “Music Player.” Other labels are,optionally, used for various application icons. In some embodiments, alabel for a respective application icon includes a name of anapplication corresponding to the respective application icon. In someembodiments, a label for a particular application icon is distinct froma name of an application corresponding to the particular applicationicon.

FIG. 4B illustrates an exemplary user interface on a device (e.g.,device 300, FIG. 3) with a touch-sensitive surface 451 (e.g., a tabletor touchpad 355, FIG. 3) that is separate from the display 450 (e.g.,touch screen display 112). Device 300 also, optionally, includes one ormore contact intensity sensors (e.g., one or more of sensors 359) fordetecting intensity of contacts on touch-sensitive surface 451 and/orone or more tactile output generators 357 for generating tactile outputsfor a user of device 300.

Although some of the examples that follow will be given with referenceto inputs on touch screen display 112 (where the touch-sensitive surfaceand the display are combined), in some embodiments, the device detectsinputs on a touch-sensitive surface that is separate from the display,as shown in FIG. 4B. In some embodiments, the touch-sensitive surface(e.g., 451 in FIG. 4B) has a primary axis (e.g., 452 in FIG. 4B) thatcorresponds to a primary axis (e.g., 453 in FIG. 4B) on the display(e.g., 450). In accordance with these embodiments, the device detectscontacts (e.g., 460 and 462 in FIG. 4B) with the touch-sensitive surface451 at locations that correspond to respective locations on the display(e.g., in FIG. 4B, 460 corresponds to 468 and 462 corresponds to 470).In this way, user inputs (e.g., contacts 460 and 462, and movementsthereof) detected by the device on the touch-sensitive surface (e.g.,451 in FIG. 4B) are used by the device to manipulate the user interfaceon the display (e.g., 450 in FIG. 4B) of the multifunction device whenthe touch-sensitive surface is separate from the display. It should beunderstood that similar methods are, optionally, used for other userinterfaces described herein.

Additionally, while the following examples are given primarily withreference to finger inputs (e.g., finger contacts, finger tap gestures,finger swipe gestures), it should be understood that, in someembodiments, one or more of the finger inputs are replaced with inputfrom another input device (e.g., a mouse-based input or stylus input).For example, a swipe gesture is, optionally, replaced with a mouse click(e.g., instead of a contact) followed by movement of the cursor alongthe path of the swipe (e.g., instead of movement of the contact). Asanother example, a tap gesture is, optionally, replaced with a mouseclick while the cursor is located over the location of the tap gesture(e.g., instead of detection of the contact followed by ceasing to detectthe contact). Similarly, when multiple user inputs are simultaneouslydetected, it should be understood that multiple computer mice are,optionally, used simultaneously, or a mouse and finger contacts are,optionally, used simultaneously.

FIG. 5A illustrates exemplary personal electronic device 500. Device 500includes body 502. In some embodiments, device 500 can include some orall of the features described with respect to devices 100 and 300 (e.g.,FIGS. 1A-4B). In some embodiments, device 500 has touch-sensitivedisplay screen 504, hereafter touch screen 504. Alternatively, or inaddition to touch screen 504, device 500 has a display and atouch-sensitive surface. As with devices 100 and 300, in someembodiments, touch screen 504 (or the touch-sensitive surface)optionally includes one or more intensity sensors for detectingintensity of contacts (e.g., touches) being applied. The one or moreintensity sensors of touch screen 504 (or the touch-sensitive surface)can provide output data that represents the intensity of touches. Theuser interface of device 500 can respond to touches based on theirintensity, meaning that touches of different intensities can invokedifferent user interface operations on device 500.

Exemplary techniques for detecting and processing touch intensity arefound, for example, in related applications: International PatentApplication Serial No. PCT/US2013/040061, titled “Device, Method, andGraphical User Interface for Displaying User Interface ObjectsCorresponding to an Application,” filed May 8, 2013, published as WIPOPublication No. WO/2013/169849, and International Patent ApplicationSerial No. PCT/US2013/069483, titled “Device, Method, and Graphical UserInterface for Transitioning Between Touch Input to Display OutputRelationships,” filed Nov. 11, 2013, published as WIPO Publication No.WO/2014/105276, each of which is hereby incorporated by reference intheir entirety.

In some embodiments, device 500 has one or more input mechanisms 506 and508. Input mechanisms 506 and 508, if included, can be physical.Examples of physical input mechanisms include push buttons and rotatablemechanisms. In some embodiments, device 500 has one or more attachmentmechanisms. Such attachment mechanisms, if included, can permitattachment of device 500 with, for example, hats, eyewear, earrings,necklaces, shirts, jackets, bracelets, watch straps, chains, trousers,belts, shoes, purses, backpacks, and so forth. These attachmentmechanisms permit device 500 to be worn by a user.

FIG. 5B depicts exemplary personal electronic device 500. In someembodiments, device 500 can include some or all of the componentsdescribed with respect to FIGS. 1A, 1B, and 3. Device 500 has bus 512that operatively couples I/O section 514 with one or more computerprocessors 516 and memory 518. I/O section 514 can be connected todisplay 504, which can have touch-sensitive component 522 and,optionally, intensity sensor 524 (e.g., contact intensity sensor). Inaddition, I/O section 514 can be connected with communication unit 530for receiving application and operating system data, using Wi-Fi,Bluetooth, near field communication (NFC), cellular, and/or otherwireless communication techniques. Device 500 can include inputmechanisms 506 and/or 508. Input mechanism 506 is, optionally, arotatable input device or a depressible and rotatable input device, forexample. Input mechanism 508 is, optionally, a button, in some examples.

Input mechanism 508 is, optionally, a microphone, in some examples.Personal electronic device 500 optionally includes various sensors, suchas GPS sensor 532, accelerometer 534, directional sensor 540 (e.g.,compass), gyroscope 536, motion sensor 538, and/or a combinationthereof, all of which can be operatively connected to I/O section 514.

Memory 518 of personal electronic device 500 can include one or morenon-transitory computer-readable storage mediums, for storingcomputer-executable instructions, which, when executed by one or morecomputer processors 516, for example, can cause the computer processorsto perform the techniques described below, including processes 700, 900,1100, 1400, 1500, and 1800 (FIGS. 7, 9, 11, 14, 15, and 18). Acomputer-readable storage medium can be any medium that can tangiblycontain or store computer-executable instructions for use by or inconnection with the instruction execution system, apparatus, or device.In some examples, the storage medium is a transitory computer-readablestorage medium. In some examples, the storage medium is a non-transitorycomputer-readable storage medium. The non-transitory computer-readablestorage medium can include, but is not limited to, magnetic, optical,and/or semiconductor storages. Examples of such storage include magneticdisks, optical discs based on CD, DVD, or Blu-ray technologies, as wellas persistent solid-state memory such as flash, solid-state drives, andthe like. Personal electronic device 500 is not limited to thecomponents and configuration of FIG. 5B, but can include other oradditional components in multiple configurations.

As used here, the term “affordance” refers to a user-interactivegraphical user interface object that is, optionally, displayed on thedisplay screen of devices 100, 300, and/or 500 (FIGS. 1A, 3, and 5A-5B).For example, an image (e.g., icon), a button, and text (e.g., hyperlink)each optionally constitute an affordance.

As used herein, the term “focus selector” refers to an input elementthat indicates a current part of a user interface with which a user isinteracting. In some implementations that include a cursor or otherlocation marker, the cursor acts as a “focus selector” so that when aninput (e.g., a press input) is detected on a touch-sensitive surface(e.g., touchpad 355 in FIG. 3 or touch-sensitive surface 451 in FIG. 4B)while the cursor is over a particular user interface element (e.g., abutton, window, slider, or other user interface element), the particularuser interface element is adjusted in accordance with the detectedinput. In some implementations that include a touch screen display(e.g., touch-sensitive display system 112 in FIG. 1A or touch screen 112in FIG. 4A) that enables direct interaction with user interface elementson the touch screen display, a detected contact on the touch screen actsas a “focus selector” so that when an input (e.g., a press input by thecontact) is detected on the touch screen display at a location of aparticular user interface element (e.g., a button, window, slider, orother user interface element), the particular user interface element isadjusted in accordance with the detected input. In some implementations,focus is moved from one region of a user interface to another region ofthe user interface without corresponding movement of a cursor ormovement of a contact on a touch screen display (e.g., by using a tabkey or arrow keys to move focus from one button to another button); inthese implementations, the focus selector moves in accordance withmovement of focus between different regions of the user interface.Without regard to the specific form taken by the focus selector, thefocus selector is generally the user interface element (or contact on atouch screen display) that is controlled by the user so as tocommunicate the user's intended interaction with the user interface(e.g., by indicating, to the device, the element of the user interfacewith which the user is intending to interact). For example, the locationof a focus selector (e.g., a cursor, a contact, or a selection box) overa respective button while a press input is detected on thetouch-sensitive surface (e.g., a touchpad or touch screen) will indicatethat the user is intending to activate the respective button (as opposedto other user interface elements shown on a display of the device).

As used in the specification and claims, the term “characteristicintensity” of a contact refers to a characteristic of the contact basedon one or more intensities of the contact. In some embodiments, thecharacteristic intensity is based on multiple intensity samples. Thecharacteristic intensity is, optionally, based on a predefined number ofintensity samples, or a set of intensity samples collected during apredetermined time period (e.g., 0.05, 0.1, 0.2, 0.5, 1, 2, 5, 10seconds) relative to a predefined event (e.g., after detecting thecontact, prior to detecting liftoff of the contact, before or afterdetecting a start of movement of the contact, prior to detecting an endof the contact, before or after detecting an increase in intensity ofthe contact, and/or before or after detecting a decrease in intensity ofthe contact). A characteristic intensity of a contact is, optionally,based on one or more of: a maximum value of the intensities of thecontact, a mean value of the intensities of the contact, an averagevalue of the intensities of the contact, a top 10 percentile value ofthe intensities of the contact, a value at the half maximum of theintensities of the contact, a value at the 90 percent maximum of theintensities of the contact, or the like. In some embodiments, theduration of the contact is used in determining the characteristicintensity (e.g., when the characteristic intensity is an average of theintensity of the contact over time). In some embodiments, thecharacteristic intensity is compared to a set of one or more intensitythresholds to determine whether an operation has been performed by auser. For example, the set of one or more intensity thresholdsoptionally includes a first intensity threshold and a second intensitythreshold. In this example, a contact with a characteristic intensitythat does not exceed the first threshold results in a first operation, acontact with a characteristic intensity that exceeds the first intensitythreshold and does not exceed the second intensity threshold results ina second operation, and a contact with a characteristic intensity thatexceeds the second threshold results in a third operation. In someembodiments, a comparison between the characteristic intensity and oneor more thresholds is used to determine whether or not to perform one ormore operations (e.g., whether to perform a respective operation orforgo performing the respective operation), rather than being used todetermine whether to perform a first operation or a second operation.

In some embodiments, a portion of a gesture is identified for purposesof determining a characteristic intensity. For example, atouch-sensitive surface optionally receives a continuous swipe contacttransitioning from a start location and reaching an end location, atwhich point the intensity of the contact increases. In this example, thecharacteristic intensity of the contact at the end location is,optionally, based on only a portion of the continuous swipe contact, andnot the entire swipe contact (e.g., only the portion of the swipecontact at the end location). In some embodiments, a smoothing algorithmis, optionally, applied to the intensities of the swipe contact prior todetermining the characteristic intensity of the contact. For example,the smoothing algorithm optionally includes one or more of: anunweighted sliding-average smoothing algorithm, a triangular smoothingalgorithm, a median filter smoothing algorithm, and/or an exponentialsmoothing algorithm. In some circumstances, these smoothing algorithmseliminate narrow spikes or dips in the intensities of the swipe contactfor purposes of determining a characteristic intensity.

The intensity of a contact on the touch-sensitive surface is,optionally, characterized relative to one or more intensity thresholds,such as a contact-detection intensity threshold, a light press intensitythreshold, a deep press intensity threshold, and/or one or more otherintensity thresholds. In some embodiments, the light press intensitythreshold corresponds to an intensity at which the device will performoperations typically associated with clicking a button of a physicalmouse or a trackpad. In some embodiments, the deep press intensitythreshold corresponds to an intensity at which the device will performoperations that are different from operations typically associated withclicking a button of a physical mouse or a trackpad. In someembodiments, when a contact is detected with a characteristic intensitybelow the light press intensity threshold (e.g., and above a nominalcontact-detection intensity threshold below which the contact is nolonger detected), the device will move a focus selector in accordancewith movement of the contact on the touch-sensitive surface withoutperforming an operation associated with the light press intensitythreshold or the deep press intensity threshold. Generally, unlessotherwise stated, these intensity thresholds are consistent betweendifferent sets of user interface figures.

An increase of characteristic intensity of the contact from an intensitybelow the light press intensity threshold to an intensity between thelight press intensity threshold and the deep press intensity thresholdis sometimes referred to as a “light press” input. An increase ofcharacteristic intensity of the contact from an intensity below the deeppress intensity threshold to an intensity above the deep press intensitythreshold is sometimes referred to as a “deep press” input. An increaseof characteristic intensity of the contact from an intensity below thecontact-detection intensity threshold to an intensity between thecontact-detection intensity threshold and the light press intensitythreshold is sometimes referred to as detecting the contact on thetouch-surface. A decrease of characteristic intensity of the contactfrom an intensity above the contact-detection intensity threshold to anintensity below the contact-detection intensity threshold is sometimesreferred to as detecting liftoff of the contact from the touch-surface.In some embodiments, the contact-detection intensity threshold is zero.In some embodiments, the contact-detection intensity threshold isgreater than zero.

In some embodiments described herein, one or more operations areperformed in response to detecting a gesture that includes a respectivepress input or in response to detecting the respective press inputperformed with a respective contact (or a plurality of contacts), wherethe respective press input is detected based at least in part ondetecting an increase in intensity of the contact (or plurality ofcontacts) above a press-input intensity threshold. In some embodiments,the respective operation is performed in response to detecting theincrease in intensity of the respective contact above the press-inputintensity threshold (e.g., a “down stroke” of the respective pressinput). In some embodiments, the press input includes an increase inintensity of the respective contact above the press-input intensitythreshold and a subsequent decrease in intensity of the contact belowthe press-input intensity threshold, and the respective operation isperformed in response to detecting the subsequent decrease in intensityof the respective contact below the press-input threshold (e.g., an “upstroke” of the respective press input).

In some embodiments, the device employs intensity hysteresis to avoidaccidental inputs sometimes termed “jitter,” where the device defines orselects a hysteresis intensity threshold with a predefined relationshipto the press-input intensity threshold (e.g., the hysteresis intensitythreshold is X intensity units lower than the press-input intensitythreshold or the hysteresis intensity threshold is 75%, 90%, or somereasonable proportion of the press-input intensity threshold). Thus, insome embodiments, the press input includes an increase in intensity ofthe respective contact above the press-input intensity threshold and asubsequent decrease in intensity of the contact below the hysteresisintensity threshold that corresponds to the press-input intensitythreshold, and the respective operation is performed in response todetecting the subsequent decrease in intensity of the respective contactbelow the hysteresis intensity threshold (e.g., an “up stroke” of therespective press input). Similarly, in some embodiments, the press inputis detected only when the device detects an increase in intensity of thecontact from an intensity at or below the hysteresis intensity thresholdto an intensity at or above the press-input intensity threshold and,optionally, a subsequent decrease in intensity of the contact to anintensity at or below the hysteresis intensity, and the respectiveoperation is performed in response to detecting the press input (e.g.,the increase in intensity of the contact or the decrease in intensity ofthe contact, depending on the circumstances).

For ease of explanation, the descriptions of operations performed inresponse to a press input associated with a press-input intensitythreshold or in response to a gesture including the press input are,optionally, triggered in response to detecting either: an increase inintensity of a contact above the press-input intensity threshold, anincrease in intensity of a contact from an intensity below thehysteresis intensity threshold to an intensity above the press-inputintensity threshold, a decrease in intensity of the contact below thepress-input intensity threshold, and/or a decrease in intensity of thecontact below the hysteresis intensity threshold corresponding to thepress-input intensity threshold. Additionally, in examples where anoperation is described as being performed in response to detecting adecrease in intensity of a contact below the press-input intensitythreshold, the operation is, optionally, performed in response todetecting a decrease in intensity of the contact below a hysteresisintensity threshold corresponding to, and lower than, the press-inputintensity threshold.

Attention is now directed towards embodiments of user interfaces (“UI”)and associated processes that are implemented on an electronic device,such as portable multifunction device 100, device 300, or device 500.

FIGS. 6A-6F illustrate exemplary user interfaces for sharing one or morepasses in accordance with some embodiments. The user interfaces in thesefigures are used to illustrate the processes described below, includingthe processes in FIG. 7.

FIG. 6A illustrates device 600 a, which includes display 602 a (e.g., atouch screen display). In FIG. 6A, device 600 a displays user interface604, which includes information about three passes associated with aservice provider, named Amusement World (e.g., an amusement park). Insome embodiments, a pass is a digital pass that includes data that canbe transmitted (e.g., to a pass reader terminal) to use or redeem thepass. In some embodiments, the service provider is a business thatprovides access to a service (e.g., an amusement park, a concert venue,and/or a merchant with memberships). In some embodiments, the serviceprovider is an entity (e.g., a company and/or a third party) that isdifferent from the entity (e.g., the first party) that developed and/orprovides device 600 a and/or the operating system being run on device600 a. In some embodiments, user interface 604 is a user interface for avendor application (e.g., a third-party application), a vendor website(e.g., a third-party website), or a wallet application (e.g., afirst-party wallet application included with the operating system ofdevice 600 a). In some embodiments, user interface 604 includesinformation about one pass, two passes, or more than three passes. Insome embodiments, the passes include electronic tickets, electronicmembership cards, or electronic access badges. In some embodiments, thepasses provide access to a service provided by the service provider(e.g., entry into an amusement park, entry into a venue, entry into aretail establishment, access to an account or account feature, and/orredemption of an offer or promotion). In the embodiment illustrated inFIG. 6A, the passes provide access to a venue called Amusement World.

User interface 604 includes affordance 606, which when selected,initiates a process for adding the passes to an account associated witha first user identity (e.g., an account associated with a user or ownerof device 600 a and to which device 600 a is signed into). In someembodiments, the account is for a first-party wallet applicationassociated with the user identity. In some embodiments, a first-partyapplication is an application that is developed, managed, and/orprovided by the developer of device 600 a and/or the operating systembeing run on device 600 a. In FIG. 6A, while displaying user interface604, device 600 a receives (e.g., detects) a request 603 to add thepasses indicated on user interface 604 a to an account associated with afirst user identity. In the embodiment illustrated in FIG. 6A, request603 includes a selection of (e.g., a tap on) affordance 606.

After (e.g., in response to) receiving request 603 device 600 a displaysa share affordance 612 a (e.g., as shown on user interface 608 a in FIG.6B) for providing (e.g., sharing) at least one of the one or more passesto an account associated with a second user identity.

Use interface 608 a includes (e.g., concurrently displays) shareaffordance 612 a, add affordance 610 a, a representation 630 a of thepass(es) (or an account associated with the pass(es) and/or the serviceprovider), and a prompt to add the passes to the account associated withthe first user identity. In some embodiments, user interface 608 a isdisplayed in response to receiving a request to launch or open thewallet account application (e.g., a double press of hardware button 635a on device 600 a) after receiving request 603 to add the one or morepasses to the account associated with the first user identity.

While displaying user interface 608 a, device 600 a can receive (e.g.,detect) request 605 (e.g., a tap on add affordance 610 a) to add thepasses to the account associated with the first user identity and/or todevice 600 a (e.g., the passes can be stored on device 600 a). In someembodiments, adding a pass to an account associated with a user identityincludes adding data corresponding to the pass to the account withoutadding (e.g., storing) data corresponding to the pass to a deviceassociated with the user identity, adding data corresponding to the passto the account and adding data corresponding to the pass to a deviceassociated with the user identity, or adding data corresponding to thepass to a device associated with the user identity without adding datacorresponding to the pass to the account.

In the embodiment illustrated in FIG. 6C, in response to receivingrequest 605, device 600 a removes (e.g., ceases display of) the promptfor the user to add the passes to the account associated with the firstuser identity and displays an indication (e.g., a textual indication “3PASSES ADDED TO WALLET”) that the passes have been added to the accountassociated with the first user identity. In the embodiment illustratedin FIG. 6C, in response to receiving request 605, device 600 a removes(e.g., ceases display of) add affordance 610 a and displays Doneaffordance 632.

In some embodiments, device 600 a (e.g., automatically, withoutadditional user input) adds all of the received passes to the accountand/or device associated with the first user identity in response toreceiving selection of add affordance 610 a. In some embodiments, inresponse to receiving selection of add affordance 610 a, device 600 aprovides (e.g., displays) one or more options (e.g., affordances) toselect which of the received passes to add to the account and/or deviceassociated with the first user identity. For example, device 600 a canprovide the ability to add the passes one at a time or to add any one ortwo of the three passes without adding all of the passes.

In some embodiments, share affordance 612 a is displayed after addingthe pass(es) (e.g., information corresponding to the pass(es)) to theaccount associated with the first user identity. For example, shareaffordance 612 a is not displayed in user interface 608 a in FIG. 6B inresponse to receiving request 603 in FIG. 6A, and is displayed in userinterface 608 a in FIG. 6C after adding the pass(es) to the accountassociated with the first user identity (e.g., in response to receivingselection 605 in FIG. 6B of add affordance 610 a).

In some embodiments, device 600 a provides capability to select a visualdesign for the pass(es) (e.g., different artwork options that can beused as an image on the passes). In some embodiments, prior to sharingthe pass(es) and/or adding the pass(es) to device 600 a (or an accountassociated with device 600 a), device 600 a receives a request to viewvisual design options for the pass(es) (e.g., device 600 a detectsselection of an affordance that, when selected, causes device 600 a todisplay selectable visual design options). For example, device 600 areceives an input corresponding to a selection of a visual design forthe one or more passes, and in response, displays the pass(es) accordingto the selected visual design. In some embodiments, data representingthe visual design is provided to the account associated with the seconduser identity.

In some embodiments, the representation of the pass(es) (e.g., in userinterface 608 a, 608 b, and/or 618) is displayed with a geometryalteration effect (e.g., a skewing effect, a 3D effect, a depth effect,and/or a parallax effect). In some embodiments, the representation ofthe pass(es) includes a graphical animation (e.g., shifting colorsand/or shifting shapes) that creates an illusion that the representationof the pass(es) (or a portion thereof) is a three dimensional objectthat is being viewed from different angles as the angle (or orientation)of the device (e.g., 600 a or 600 b) changes. In some embodiments, thegeometry alternation effect includes shifting the position of a firstlayer (e.g., a first pass and/or a first layer of artwork) relative to asecond layer (e.g., a second pass and/or a second layer of artwork(e.g., a background)) based on a change in orientation of the devicerelative to a reference point. In some embodiments, displaying thegeometry alternation includes detecting a change in orientation of thedevice relative to a fixed reference point on the earth (e.g., based onorientation sensors of the device such as an accelerometer, a gyroscope,and/or a magnetometer). In some embodiments, displaying the geometryalternation effect includes detecting a change in orientation of a userrelative to the device (e.g., based on a face tracking sensor such as acamera or other face tracking sensor that can detect changes of thepoint of view of a viewing angle of the device by a face that is beingtracked by the device).

In some embodiments, the display of the representation of the pass(es)(e.g., in user interface 608 a, 608 b, and/or 618) includes an animation(e.g., twinkling stars; an ongoing animation; and/or a repeatinganimation). In some embodiments, displaying the representation of thepass(es) includes displaying an animation of at least one visual featureof the representation of the pass(es) (e.g., stars on the pass areanimated to twinkle). In some embodiments, the animation includesdisplaying a plurality of intermediate states while transitioning froman initial state of the visual feature to an end state of the visualfeature.

In FIG. 6C, device 600 a receives (e.g., detects) input 609 (e.g., atap) corresponding to selection of share affordance 612 a. In responseto receiving input 609, device 600 a initiates a process for providingat least one of the passes to the account associated with the seconduser identity. In some embodiments, the account associated with thesecond user identity is a second account for the first-party walletapplication associated with a second user (e.g., an account of a familymember). In the embodiment illustrated in FIG. 6D, the process forproviding at least one of the passes to the account associated with thesecond user identity includes displaying user interface 614. In someembodiments, user interface 614 includes a graphical element having anappearance of a card or a sheet that overlaps (e.g., is displayed infront of) at least a portion of user interface 608 a. User interface 614includes a graphical representation (e.g., a list) of one or more useridentities and a graphical representation of one or more methods forproviding the pass(es) (e.g., text message, email, NFC, and/or a sharedcloud storage account shared by the first user identity and the seconduser identity).

In FIG. 6D, device 600 a receives (e.g., detects) input 611 (e.g., atap) selecting a user identity (e.g., a tap on representation 616 of auser identity associated with user Amy Appleseed). In response toreceiving input 611, device 600 a provides at least one of the passes toan account associated with the selected user identity (e.g., informationis added to the account associated with the selected user identity suchthat at least one pass is redeemable from a wallet application of thesecond user identity). In some embodiments, device 600 a provides theone or more passes by sending information representing the pass orproviding access to the pass information from a central server. In theembodiment illustrated in FIG. 6D, device 600 a provides one of thepasses (e.g., only one of the passes; a single pass) to the accountassociated with the selected user identity.

In some embodiments, in response to receiving input 611, device 600 adisplays (e.g., returns to) user interface 608 a shown in FIG. 6C. Insome embodiments (e.g., after returning to user interface 608 a shown inFIG. 6C), device 600 a provides at least one of the passes to an accountassociated with a second user identity (e.g., a selected user identity)in response to receiving input 609 (e.g., selection of share affordance612 a).

In some embodiments, some or all of the techniques described withreference to FIGS. 6A-6D can be repeated to provide the pass(es) toanother user identity. For example, after (e.g., in response to)selection of the second user identity in user interface 614 (or afterproviding the pass(es) to the account associated with the second useridentity), device 600 a displays user interface 608 a as shown in FIG.6B, if the pass(es) have not been added to device 600 a, or userinterface 608 a as shown in FIG. 6C, optionally without Done affordance632, if the pass(es) have been added to device 600 a. In someembodiments, two or more user identities (e.g., Amy Appleseed and JohnAppleseed) can be selected in user interface 614, and in response toreceiving selection of two or more user identities, device 600 aprovides the pass(es) to accounts associated with all of the selecteduser identities. In some embodiments, a representation in user interface614 corresponds to a group of user identities (e.g., two or more useridentities), and in response to receiving selection of such arepresentation, device 600 a provides the pass(es) to accountsassociated with all of the user identities associated with the group.

In some embodiments, device 600 a (e.g., automatically, withoutadditional user input) provides all of the received passes to theaccount associated with the selected user identity in response toreceiving input 611. In some embodiments, in response to receiving input611, device 600 a provides (e.g., displays) one or more options (e.g.,affordances) to select which of the passes to provide to the accountassociated with the selected user identity. For example, device 600 acan provide the ability to provide the passes one at a time or toprovide any one or two of the three passes without providing all of thepasses.

In the embodiment illustrated in FIGS. 6A-6C, share affordance 612 a isdisplayed as part of a process of adding the passes to device 600 aand/or the account associated with a user identity associated withdevice 600 a. For example, the passes are added to device 600 a inresponse to receiving selection 605 of add affordance 610 a in FIG. 6Bprior to providing the pass to an account associated with a second useridentity. In some embodiments, one or more passes can be provided to anaccount associated with a second user identity prior to or withoutadding the pass(es) to device 600 a. For example, device 600 a canreceive (e.g., detect) input 607 (e.g., a tap) corresponding toselection of share affordance 612 a, as shown in FIG. 6B. In response toreceiving input 607, device 600 a initiates the process for providing atleast one of the passes to the account associated with the second useridentity described above with reference to FIG. 6D (e.g., device 600 adisplays user interface 614) without or prior to adding the pass(es) todevice 600 a.

In some embodiments, after the pass(es) are shared, device 600 a returnsto an application or website that generated the pass(es) (e.g., a sourceof the pass(es)) or from which the process for adding the pass(es) tothe account associated with the first user identity was initiated. Forexample, in response to selection of a second user identity, such asinput 611 on representation 616, device 600 a displays (e.g.,automatically; without further user input) a user interface of theapplication corresponding to user interface 604 in FIG. 6A (e.g., device600 a launches, re-opens, brings to the foreground, and/or switches to athird-party application or website of the service provider that was thesource of the pass(es) or from which the process for adding the pass(es)to an account associated with the first user identity was initiated.

In some embodiments, the second user identity is associated with thefirst user identity (e.g., the two user identities are included in afamily sharing account in which users can share data such as photos,videos, passes, and/or access to other accounts). In some suchembodiments, providing the pass(es) to the account associated with thesecond user identity adds the pass(es) to the account associated withthe second user identity without input at a computer system associatedwith the second user identity and/or without providing a notification ormessage at a device associated with the second user identity (e.g., thepass(es) appear in the account of the second user identity (e.g., aredisplayed in a wallet application that is logged into the account of thesecond user identity) without sending a text message, email, and/orother notification.

In some embodiments, providing the pass(es) to the account associatedwith the second user identity adds the pass(es) to a first deviceassociated with the second user identity (e.g., a phone) and a seconddevice associated with the second user identity (e.g., a watch).

In some embodiments, adding the pass(es) to the account and/or device(s)associated with the first user identity or the second user identityauthorizes the respective devices to redeem the pass(es).

In some embodiments, an animation (e.g., a spaceship launching and/or agate opening) is displayed when the pass(es) are redeemed or used (e.g.,as described with reference to FIGS. 8C and 8E). For example, in someembodiments, device 600 a detects a request (e.g., a request asdescribed with reference to FIGS. 8C and 8E) to provide datacorresponding to a first pass of the pass(es) to a pass reader terminal,and in response, displays an animation associated with the first passindicating that the data corresponding to the first pass wassuccessfully provided to the pass reader terminal. In some embodiments,the animation includes displaying a transition from an initial state(e.g., spaceship on launch pad and/or gate closed) to an end state(e.g., spaceship in space and/or gate open), and a plurality ofintermediate states are displayed while transitioning from the initialstate to the end state. In some embodiments, the animation is displayedin response to detecting that the data corresponding to the first passwas transmitted from the computer system. In some embodiments, theanimation is displayed in response to receiving a confirmation that thedata corresponding to the first pass was accepted by the pass readerterminal.

In some embodiments, when the pass(es) are used, device 600 a and/or thepass reader terminal make (e.g., output) a unique noise or a noisedifferent from noises made when other events occur. In some embodiments,the noise includes a sound that corresponds to custom art or animation(e.g., a sound of the spaceship launching and/or a sound associated witha visual design selected by a user). For example, in some embodiments,device 600 a detects a request to provide data corresponding to a passto a pass reader terminal, and in response, causes (e.g., by the device600 a and/or the pass reader terminal) an audio notificationcorresponding to the pass (e.g., when the pass is used, the user'sdevice and/or the pass reader terminal plays a sound corresponding toartwork on the pass). In some embodiments, the audio notification iscustom to the pass (e.g., the notification is a specific audio output(e.g., a sound effect) associated with the pass that is different from anotification for alerts, such as incoming calls, text messages, and/oremails).

Returning to FIG. 6D, representation 616 corresponds to an option toprovide one or more of the passes to an account associated with a useridentity associated with user Amy Appleseed via text message, asindicated by the thought bubble indication on the bottom right ofrepresentation 616. In some embodiments, the account associated with theselected user identity is accessed via a second electronic deviceassociated with the second user identity. FIG. 6E illustrates an exampleof a user interface 618 of a messaging application displayed on display602 b of device 600 b associated with the selected user identity (e.g.,Amy Appleseed's phone). User interface 618 includes (e.g., displays) amessage conversation between the user identity associated with device600 a and the user identity associated with device 600 b. As a result ofthe user identity associated with device 600 b being selected in FIG.6D, user interface 618 includes (e.g., in the message conversation) agraphical indication 620 of the pass(es) and affordance 622 for viewingthe shared pass(es).

In FIG. 6E, device 600 b receives (e.g., detects) request 613 to viewthe shared pass(es) (e.g., a tap on affordance 622). In response toreceiving request 613, device 600 b displays user interface 608 b, asshown in FIG. 6F. In some embodiments, user interface 608 b is a userinterface for a wallet application (e.g., a first-party walletapplication) associated with the user identity associated with device600 b. In some embodiments, user interface 608 b is similar to userinterface 608 a shown in FIG. 6B. User interface 608 b includes (e.g.,concurrently displays) share affordance 612 b, add affordance 610 b, arepresentation 630 b of the shared pass(es) (or an account associatedwith the shared pass(es) and/or the service provider), and a prompt toadd the pass(es) to the account associated with the first user identity.In some embodiments, user interface 608 b is displayed in response toreceiving a request to launch or open the wallet account application(e.g., a double press of hardware button 635 b on device 600 b) afterreceiving the pass(es). For example, the option to add and/or share thereceived pass(es) can be displayed in the wallet application associatedwith the selected user identity without (or prior to) viewingrepresentation 620 of the pass(es) in user interface 618 of themessaging application or selecting affordance 622.

In response to receiving selection of add affordance 610 b, device 600 badds the pass(es) to an account (e.g., a digital wallet account)associated with the user identity associated with device 600 b. In someembodiments, the shared passes are added to the account associated withthe second user identity without further input (e.g., without selectionof add affordance 610 b in user interface 608 b, without input at device600 b, and/or without other confirmation input). In some embodiments,the shared pass(es) are automatically added to the account associatedwith the selected user identity, but further input is required (e.g.,selection of add affordance 610 b) to add/store the shared pass(es) ondevice 600 b. In some embodiments, selection of add affordance 610 b (orother input at a device associated with the selected user identity(e.g., a confirmation input)) is required to add the shared pass(es) tothe account associated with the selected user identity.

In response to receiving selection of share affordance 612 b, device 600b initiates a process to share the pass with another user identity(e.g., a same or similar process as described for device 600 a withreference to FIGS. 6C-6D).

FIG. 7 is a flow diagram illustrating a method for sharing one or morepasses in accordance with some embodiments. Method 700 is performed at acomputer system (e.g., 100, 300, 500, 600 a) in communication with adisplay generation component (e.g., 602 a) and one or more input devices(e.g., a touch-sensitive surface). Some operations in method 700 are,optionally, combined, the orders of some operations are, optionally,changed, and some operations are, optionally, omitted.

As described below, method 700 provides an intuitive way for sharingpasses with an account associated with a second user identity. Themethod reduces the cognitive burden on a user when sharing passes,thereby creating a more efficient human-machine interface. Forbattery-operated computer systems, enabling a user to share passesfaster and more efficiently conserves power and increases the timebetween battery charges.

In method 700, the computer system (e.g., 600 a) displays (702), via thedisplay generation component (e.g., 602 a), a first user interface(e.g., 604, 608 a) (e.g., a vendor application, a vendor website, and/ora wallet application) that includes information about one or more passesassociated with a service provider (e.g., a business that providesaccess to a service (e.g., an amusement park, a concert venue, and/or amerchant with memberships)).

While displaying the first user interface, the computer system receives(704), via the one or more input devices, a request (e.g., 603, 605)(e.g., selection of an “add to wallet” affordance via a touch-sensitivesurface) to add one or more passes (e.g., electronic tickets, electronicmembership cards, and/or electronic access badges) to an accountassociated with a first user identity (e.g., an account for afirst-party wallet application associated with the user). The one ormore passes provide access to a service provided by the service provider(e.g., entry into an amusement park, entry into a venue, entry into aretail establishment, access to an account or account feature, and/orredemption of an offer or promotion).

After receiving the request (and optionally after adding informationcorresponding to the one or more passes to the account associated withthe first user identity (e.g., adding information such that the passesare redeemable from the wallet application)), the computer systemdisplays (706), via the display generation component, a share affordance(e.g., 612 a) (e.g., a selectable user interface object) for providing(e.g., sending information representing the pass and/or providing accessto the pass information from a central server) at least one of the oneor more passes to an account associated with a second user identity(e.g., a second account for the first-party wallet applicationassociated with a second user (e.g., an account of a family member). Insome embodiments, the account associated with the second user identityis accessed via a second electronic device (e.g., 600 b) associated withthe second user identity).

The computer system receives (708), via the one or more input devices, auser input (e.g., 607, 609) corresponding to selection of the shareaffordance (e.g., 612 a) (e.g., a tap gesture, via a touch-sensitivesurface, on the share affordance).

In response to receiving the user input corresponding to selection ofthe share affordance, the computer system initiates (710) a process forproviding at least one of the one or more passes to the accountassociated with the second user identity (e.g., adding information tothe second account such that at least one pass is redeemable from thewallet application of the second user). Providing passes to a secondaccount associated with a second user identity in response selection ofa share affordance reduces the number of inputs needed to add passes tothe second account. Reducing the number of inputs needed to perform anoperation enhances the operability of the computer system and makes theuser-system interface more efficient (e.g., by helping the user toprovide proper inputs and reducing user mistakes whenoperating/interacting with the computer system) which, additionally,reduces power usage and improves battery life of the computer system byenabling the user to use the computer system more quickly andefficiently.

In some embodiments, before initiating the process for providing atleast one of the one or more passes to the account associated with thesecond user identity, the second user identity is selected from a listof user identities available to receive a shared pass (e.g., selectedfrom user interface 614) (e.g., family members and/or contacts in acontact list). In some embodiments, the process for providing at leastone of the one or more passes to the second account associated with thesecond user identity includes receiving and responding to a sequence ofone or more inputs and can include displaying one or more userinterfaces. In some embodiments, the process for providing at least oneof the one or more passes to the second account associated with thesecond user identity includes providing an indication (e.g., 620) (e.g.,a text message) to a device associated with the second user identitythat the pass has been added to (e.g., authorized to be redeemed by) theaccount associated with the second user identity).

In some embodiments, displaying the first user interface (e.g., 604, 608a) includes displaying a representation (e.g., 630 a) of the one or morepasses with a geometry alteration effect (e.g., a skewing effect, a 3Deffect, a depth effect, a parallax effect, and/or a graphical animation(e.g., shifting colors and/or shifting shapes) that creates an illusionthat the representation of the one or more passes (or portion thereof)is a three dimensional object that is being viewed from different anglesas the angle (or orientation) of the display generation componentchanges). In some embodiments, the geometry alternation effect includesshifting the position of a first layer (e.g., a first pass and/or afirst layer of artwork) relative to a second layer (e.g., a second passand/or a second layer of artwork (e.g., a background)) based on a changein orientation of the display generation component relative to areference point. In some embodiments, displaying the geometryalternation includes detecting a change in orientation of the displaygeneration component relative to a fixed reference point on the earth(e.g., based on orientation sensors of the computer system such as anaccelerometer, a gyroscope, and/or a magnetometer). In some embodiments,displaying the geometry alternation effect includes detecting a changein orientation of a user relative to the display generation component(e.g., based on a face tracking sensor such as a camera or other facetracking sensor that can detect changes of the point of view of aviewing angle of the device by a face that is being tracked by thedevice). Displaying a representation of the one or more passes with ageometry alteration effect provides the user with visual feedback abouta state of the display generation component and/or information about theone or more passes, such as how many passes are available (e.g., byallowing the height of a simulated stack of passes to be viewed bychanging the orientation of the display generation component). Further,displaying the geometry alteration effect as the orientation of thedisplay generation component changes indicates to the user that thedisplayed passes are authentic and not a video that is displayedindependently of the orientation of the display generation component.Providing improved visual feedback to the user enhances the operabilityof the computer system and makes the user-system interface moreefficient (e.g., by helping the user to provide proper inputs andreducing user mistakes when operating/interacting with the computersystem) which, additionally, reduces power usage and improves batterylife of the device by enabling the user to use the device more quicklyand efficiently.

In some embodiments, in response to receiving the request (e.g., 603,605) to add one or more passes to the account associated with the firstuser identity, the computer system initiates a process for adding theone or more passes to a device (e.g., 600 a) associated with (e.g.,logged into) the account associated with the first user identity. Insome embodiments, the process for adding the one or more passes to thedevice associated with the account associated with the first useridentity includes displaying the share affordance (e.g., 612 a) forproviding at least one of the one or more passes to the accountassociated with the second user identity. Displaying the shareaffordance for providing at least one of the one or more passes to theaccount associated with the second user identity as part of the processfor adding the one or more passes to the device associated with theaccount associated with the first user identity allows the user toefficiently share passes without having to provide extra inputs tonavigate to additional user interfaces. Reducing the number of inputsneeded to perform an operation enhances the operability of the computersystem and makes the user-system interface more efficient (e.g., byhelping the user to provide proper inputs and reducing user mistakeswhen operating/interacting with the computer system) which,additionally, reduces power usage and improves battery life of thecomputer system by enabling the user to use the computer system morequickly and efficiently.

In some embodiments, in response to receiving the request (e.g., 603,605) to add one or more passes to the account associated with the firstuser identity, the computer system adds a first pass of the one or morepasses and a second pass of the one or more passes, different from thefirst pass of the one or more passes, to the account associated with thefirst user identity (e.g., a single input on an “add passes” affordance(e.g., 606, 610 a) causes multiple passes to be added to the account).Adding a first pass and a second pass to the account associated with thefirst user identity in response to receiving the request to add one ormore passes to the account associated with the first user identityallows the user to efficiently add multiple passes to the accountassociated with the first user identity with a single input. Reducingthe number of inputs needed to perform an operation enhances theoperability of the computer system and makes the user-system interfacemore efficient (e.g., by helping the user to provide proper inputs andreducing user mistakes when operating/interacting with the computersystem) which, additionally, reduces power usage and improves batterylife of the computer system by enabling the user to use the computersystem more quickly and efficiently.

In some embodiments, the request (e.g., 603) to add one or more passesto the account associated with the first user identity does not add theone or more passes to the account associated with the first useridentity. Forgoing adding the passes to the account associated with thefirst user identity allows the user to share one or more passes with anaccount associated with a second user identity without adding passes tothe account associated with the first user identity, which providesadditional control to the user over which accounts have passes.Providing additional control of the computer system to the user enhancesthe operability of the computer system and makes the user-systeminterface more efficient (e.g., by helping the user to provide properinputs and reducing user mistakes when operating/interacting with thecomputer system) which, additionally, reduces power usage and improvesbattery life of the computer system by enabling the user to use thecomputer system more quickly and efficiently.

In some embodiments, the process for providing at least one of the oneor more passes to the account associated with the second user identityincludes providing a first pass of the one or more passes and a secondpass of the one or more passes, different from the first pass of the oneor more passes, to the account associated with the second user identity.In some embodiments, the passes are sent to the account associated withthe second user identity via text message (e.g., 620), and then thesecond user is given an option to add passes (e.g., 610 b). In someembodiments, all of the passes in the one or more passes are pushed tothe account associated with the second user identity without furtherinput from the second user (e.g., in response to a single input).Providing a first pass and a second pass to the account associated withthe second user identity allows the user to efficiently share multiplepasses to the account associated with the second user identity with asingle input. Reducing the number of inputs needed to perform anoperation enhances the operability of the computer system and makes theuser-system interface more efficient (e.g., by helping the user toprovide proper inputs and reducing user mistakes whenoperating/interacting with the computer system) which, additionally,reduces power usage and improves battery life of the computer system byenabling the user to use the computer system more quickly andefficiently.

In some embodiments, the share affordance (e.g., 612 a) is displayed ina second user interface (e.g., 608 a) (e.g., a UI for a walletapplication) different from the first user interface (e.g., 604) (e.g.,a user interface of an application associated with the serviceprovider). In some embodiments, in response to receiving the user input(e.g., 607, 609) corresponding to selection of the share affordance, thecomputer system displays (e.g., automatically; without further userinput) the first user interface. Displaying the first user interface inresponse to receiving the user input corresponding to selection of theshare affordance allows the user to return to the first user interfacewithout additional input. Reducing the number of inputs needed toperform an operation enhances the operability of the computer system andmakes the user-system interface more efficient (e.g., by helping theuser to provide proper inputs and reducing user mistakes whenoperating/interacting with the computer system) which, additionally,reduces power usage and improves battery life of the computer system byenabling the user to use the computer system more quickly andefficiently.

In some embodiments, the second user identity is associated with thefirst user identity (e.g., the two users are included in a familysharing account), and the process for providing at least one of the oneor more passes to the account associated with the second user identityadds the at least one of the one or more passes to the accountassociated with the second user identity without input at a computersystem (e.g., 600 b) associated with the second user identity (e.g.,pass appears in the second user's wallet without receiving text messageand/or pass data is sent via a shared cloud storage account). Adding theat least one of the one or more passes to the account associated withthe second user identity provides additional control to the user overwhich accounts have passes. Providing additional control of the computersystem to the user enhances the operability of the computer system andmakes the user-system interface more efficient (e.g., by helping theuser to provide proper inputs and reducing user mistakes whenoperating/interacting with the computer system) which, additionally,reduces power usage and improves battery life of the computer system byenabling the user to use the computer system more quickly andefficiently.

In some embodiments, the process for providing at least one of the oneor more passes to the account associated with the second user identityadds (e.g., authorizes the devices to redeem) the at least one of theone or more passes to a first device (e.g., 600 b) associated with thesecond user identity (e.g., a phone) and a second device associated withthe second user identity (e.g., a watch). Adding the at least one of theone or more passes to a first device associated with the second useridentity and a second device associated with the second user identityallows the user to add passes to multiple devices with a single input.Reducing the number of inputs needed to perform an operation enhancesthe operability of the computer system and makes the user-systeminterface more efficient (e.g., by helping the user to provide properinputs and reducing user mistakes when operating/interacting with thecomputer system) which, additionally, reduces power usage and improvesbattery life of the computer system by enabling the user to use thecomputer system more quickly and efficiently.

In some embodiments, the computer system receives an input correspondingto a selection of a visual design for the one or more passes. In someembodiments, prior to receiving the input corresponding to a selectionof a visual design, the computer system detects a request to view visualdesign options for the one or more passes and, in response to receivingthe input corresponding to the selection of the visual design for theone or more passes, the computer system displays the one or more passesaccording to the selected visual design (e.g., different artwork optionsthat can be used as an image on the passes, such as shown in FIGS. 8Aand 8D). In some embodiments, data representing the visual design isprovided to the account associated with the second user identity.Displaying the one or more passes according to the selected visualdesign allows the user to customize the appearance of a pass, whichprovides visual feedback to the user that the pass is associated withthe user's account. Providing improved visual feedback enhances theoperability of the computer system and makes the user-system interfacemore efficient (e.g., by helping the user to provide proper inputs andreducing user mistakes when operating/interacting with the computersystem) which, additionally, reduces power usage and improves batterylife of the computer system by enabling the user to use the computersystem more quickly and efficiently.

In some embodiments, the computer system detects a request to providedata corresponding to a first pass of the one or more passes to a passreader terminal (e.g., 850, as described in reference to FIGS. 8C and8E) and, in response to detecting the request to provide datacorresponding to the first pass to the pass reader terminal, thecomputer system displays, via the display generation component, ananimation associated with the first pass (e.g., as described inreference to FIGS. 8C and 8E) indicating the data corresponding to thefirst pass was successfully provided to the pass reader terminal (e.g.,an animation is displayed when the pass is used (e.g., an expression ona character changing, a spaceship launching, and/or a gate opening). Insome embodiments, the animation includes displaying a transition from aninitial state (e.g., spaceship on launch pad and/or gate closed) to anend state (e.g., spaceship in space and/or gate open), and a pluralityof intermediate states are displayed while transitioning from theinitial state to the end state. In some embodiments, the animation isdisplayed in response to detecting the data corresponding to the firstpass was transmitted from the computer system. In some embodiments, theanimation is displayed in response to receiving a confirmation that thedata corresponding to the first pass was accepted by the pass readerterminal. Displaying the animation associated with the first passprovides visual feedback to the user confirming that the datacorresponding to the first pass was successfully provided to the passreader terminal. Providing improved visual feedback enhances theoperability of the computer system and makes the user-system interfacemore efficient (e.g., by helping the user to provide proper inputs andreducing user mistakes when operating/interacting with the computersystem) which, additionally, reduces power usage and improves batterylife of the computer system by enabling the user to use the computersystem more quickly and efficiently.

In some embodiments, the computer system displays, via the displaygeneration component, a representation (e.g., 630 a, 630 b, 806 a asshown in FIGS. 8A-8C, 806 b as shown in FIGS. 8D and 8E) of a first passof the one or more passes. In some embodiments, displaying therepresentation of the first pass includes displaying an animation of atleast one visual feature of the representation of the first pass (e.g.,stars on the pass are animated to twinkle). In some embodiments, theanimation includes displaying a plurality of intermediate states whiletransitioning from an initial state of the visual feature to an endstate of the visual feature. Displaying an animation of at least onevisual feature of the representation of the first pass provides visualfeedback to the user that the displayed representation of the first passcorresponds to an authentic pass (e.g., the displayed pass is not astill image copied from another device). Providing improved visualfeedback to the user enhances the operability of the computer system andmakes the user-system interface more efficient (e.g., by helping theuser to provide proper inputs and reducing user mistakes whenoperating/interacting with the computer system) which, additionally,reduces power usage and improves battery life of the device by enablingthe user to use the device more quickly and efficiently.

In some embodiments, the computer system detects a request to providedata corresponding to a first pass of the one or more passes to a passreader terminal (e.g., 850, as described in reference to FIGS. 8C and8E) and, in response to detecting the request to provide datacorresponding to the first pass to the pass reader terminal, thecomputer system causes (e.g., by the computer system and/or the passreader terminal) an audio notification corresponding to the first pass(e.g., when the pass is used, the user's device and/or the pass readerterminal plays a sound corresponding to artwork on the pass). In someembodiments, the audio notification is customized to the first pass(e.g., the notification is a specific audio output (e.g., a soundeffect) associated with the first pass that is different from anotification for alerts, such as incoming calls, text messages, and/oremails). Causing an audio notification corresponding to the first passin response to detecting the request to provide data corresponding tothe first pass to the pass reader terminal provides feedback to the userconfirming that the first pass has been used. Providing improvedfeedback to the user enhances the operability of the computer system andmakes the user-system interface more efficient (e.g., by helping theuser to provide proper inputs and reducing user mistakes whenoperating/interacting with the computer system) which, additionally,reduces power usage and improves battery life of the device by enablingthe user to use the device more quickly and efficiently.

In some embodiments, the computer system provides (e.g., automatically;without further user input) the at least one of the one or more passesto the account associated with the second user identity. In someembodiments, the at least one of the one or more passes is provided tothe second account associated with the second user identity in responseto initiating the process for providing at least one of the one or morepasses to the second account associated with the second user identity.In some embodiments, the at least one of the one or more passes isprovided to the second account associated with the second user identityin response to receiving the user input (e.g., 607, 609) correspondingto selection of the share affordance (e.g., 612 a). In some embodiments,the at least one of the one or more passes is provided to the secondaccount associated with the second user identity in response toreceiving another input during the process for providing at least one ofthe one or more passes to the second account associated with the seconduser identity. In some embodiments, in response to receiving the userinput corresponding to selection of the share affordance, a process isinitiated for providing at least one of the one or more passes to athird account associated with a third user identity (e.g., selecting theshare affordance shares passes to two different users). In someembodiments, before initiating the process for providing at least one ofthe one or more passes to the account associated with the second useridentity or the third user identity, the second user identity and thirduser identity are selected from a list of user identities available toreceive a shared pass (e.g., selected from user interface 614) (e.g.,family members and/or contacts in a contact list). Providing the atleast one of the one or more passes to the account associated with thesecond user identity allows the at least one of the one or more passesto be added to the account associated with the second user identitywithout additional user input. Reducing the number of user inputs neededto perform an operation enhances the operability of the computer systemand makes the user-system interface more efficient (e.g., by helping theuser to provide proper inputs and reducing user mistakes whenoperating/interacting with the computer system) which, additionally,reduces power usage and improves battery life of the device by enablingthe user to use the device more quickly and efficiently.

Note that details of the processes described above with respect tomethod 700 (e.g., FIG. 7) are also applicable in an analogous manner tothe methods described below. For example, methods 900 and 1100optionally include one or more of the characteristics of the variousmethods described above with reference to method 700. For brevity, thesedetails are not repeated below.

FIGS. 8A-8F illustrate exemplary user interfaces for providing a promptto a user to provide authorization in accordance with some embodiments.The user interfaces in these figures are used to illustrate theprocesses described below, including the processes in FIG. 9.

FIG. 8A illustrates device 800 displaying user interface 804 on display802 (e.g., a touch screen display). User interface 804 includes (e.g.,displays) representation 806 a (e.g., an image) of a pass (also referredto as pass 806 a) associated with a service provider (e.g., a pass to anamusement park called Amusement World, as shown in FIG. 8A). Pass 806 aincludes text indicating that pass 806 a is associated with a person(e.g., a guest named Amy) and a logo for the service provider (e.g., acharacter and/or a robot).

In some embodiments, user interface 804 is displayed in response to auser input selecting pass 806 a. In some embodiments, user interface 804is displayed in response to receiving (e.g., detecting) an input (e.g.,a double press of hardware button 835). In some embodiments, pass 806 ais displayed in response to a user input causing data for the first passto be provided to a pass reader (e.g., 850 shown in FIG. 8C).

User interface 804 includes indication 808 a (e.g., paging dots) showingthat pass 806 a is one (e.g., the first) of a set of multiple (e.g.,three) passes (e.g., the left paging dot is highlighted and/or filledcompared to the center dot and the right dot). In FIG. 8A, userinterface 804 includes a prompt (e.g., a graphical element) for a userto hold device 800 near a pass reader terminal (e.g., to redeem pass 806a). In some embodiments, in response to device 800 being held near apass reader terminal, device 800 provides data corresponding to pass 806a to a pass reader terminal.

FIG. 8B illustrates an embodiment of user interface 804 that is similarto the embodiment shown in FIG. 8A, except that indication 808 b isdisplayed (e.g., instead of indication 808 a). Indication 808 b includesa representation of the set of three passes in a staggered stack suchthat at least a portion of each card is displayed (e.g., so that a usercan see how many passes are in the set).

FIG. 8C illustrates device 800 being held near pass reader terminal 850.In FIG. 8C, device 800 detects that data corresponding to pass 806 a wasprovided by device 800 to pass reader terminal 850. In some embodiments,the data corresponding to pass 806 a is provided via a signal from a NFCtransceiver, an optical scan, or a communication (e.g., a confirmationmessage from a remote server) indicating that a visual representation ofpass 806 a, such as a barcode or QR code, has been optically scanned. Insome embodiments, device 800 provides the data corresponding to pass 806a to pass reader terminal 850 in response to receiving (e.g., detecting)an input (e.g., authorization; contact on display 802, motion of device800, rotation of a rotatable input device, biometric information orauthentication (e.g., fingerprint data, facial data, and/or iris data),and/or a press of a hardware button on device 800).

After (e.g., in response to) detecting that data corresponding to pass806 a was provided by device 800 to pass reader terminal 850, device 800displays representation 806 a of the pass and an indication that datacorresponding to pass 806 a was provided by device 800 to pass readerterminal 850 (e.g., a checkmark icon and/or an animation of arepresentation of pass 806 a). In some embodiments, display 802 isdeactivated (e.g., off and/or in a sleep mode) before the data isprovided to pass reader terminal 850 (e.g., display 802 is activated(e.g., turned on) in response to detecting that data corresponding topass 806 a was provided by device 800 to pass reader terminal 850).

In the embodiment illustrated in FIG. 8C, the indication that datacorresponding to pass 806 a was provided by device 800 to pass readerterminal 850 includes displaying a check mark icon (e.g., in place ofthe icon above text “HOLD NEAR READER” in FIGS. 8A and 8B) anddisplaying, on pass 806 a, stars (e.g., an animation of stars twinkling)and an updated version of the logo of the service provider (e.g., ananimation of the robot raising its right arm/hand). In some embodiments,after (e.g., in response to) detecting that data corresponding to pass806 a was provided by device 800 to pass reader terminal 850, device 800provides a tactile and/or audible output, as indicated by the wavy linesaround the corners of device 800 in FIG. 8C. In some embodiments, after(e.g., in response to) detecting that data corresponding to pass 806 awas provided by device 800 to pass reader terminal 850, pass readerterminal 850 provides an indication (e.g., audible output and/or anoise).

In some embodiments, in accordance with a determination that datacorresponding to a second pass is available to be provided to passreader terminal 850 by device 800, device 800 provides a prompt (e.g., avisual, audible, and/or tactile prompt) to provide authorization fordata corresponding to the second pass to be provided to pass readerterminal 850 by device 800. In some embodiments, in accordance with thedetermination that data corresponding to a second pass is available tobe provided to pass reader terminal 850 by device 800, device 800maintains display 802 in an active state (e.g., display 800 is turnedon).

In some embodiments, pass 806 a and the second pass are associated witheach other (e.g., both passes provide access to the same event and/orday/time at the service provider). In some embodiments, other passes fora different event or time/day at the service provider are not used(e.g., do not cause a prompt that data corresponding to a second pass isavailable). In some embodiments, a prompt is provided only foradditional passes that are associated with pass 806 a.

In some embodiments, providing the prompt includes displaying anindication that data corresponding to at least the second pass isavailable to be provided to pass reader terminal 850 by device 800(e.g., displaying paging dots, displaying a representation of a stack ofpasses, displaying an instruction to tap the screen, displaying aninstruction to swipe, displaying an instruction to tilt the phone,and/or display a portion of a second pass along an edge of the display).In the embodiment illustrated in FIG. 8C, the prompt includes displayingthe text “ADVANCE TO NEXT PASS” and displaying (e.g., maintainingdisplay of) indication 808 a. In some embodiments, the prompt indicatesa number of passes available to be provided to the pass reader terminalby device 800 (e.g., paging dots 808 a and/or a representation of astack of passes 808 b). In some embodiments, providing the promptincludes outputting an audio notification that data corresponding to thesecond pass is available to be provided to pass reader terminal 850 bydevice 800. In some embodiments, providing the prompt includesoutputting, via one or more tactile output generators, a tactile output(e.g., vibration) when data corresponding to the second pass isavailable to be provided to pass reader terminal 850 by device 800.

In some embodiments, in accordance with a determination that datacorresponding to a second pass is not available to be provided to passreader terminal 850 by device 800, device 800 forgoes providing theprompt to provide authorization for data corresponding to a second passto be provided to pass reader terminal 850 by device 800. In someembodiments, in accordance with the determination that datacorresponding to a second pass is not available to be provided to passreader terminal 850 by device 800, device 800 deactivates display 802(e.g., display 802 is turned off and/or transitioned to a lower powerstate (e.g., a state with low brightness and/or refresh rate)).

FIG. 8D illustrates device 800 displaying representation 806 b of asecond pass (also referred to as pass 806 b). In FIG. 8D, the centerpaging dot of paging dots 808 a is highlighted and/or filled compared tothe left dot and the right dot to indicate that pass 806 b is the secondof three passes. Pass 806 b includes text indicating that pass 806 b isassociated with a person (e.g., a guest named Pete and/or a differentperson than for pass 806 a) and a logo for the service provider (e.g., adifferent logo than for pass 806 a; a character; and/or a mouse).Similar to user interface 804 in FIG. 8A, user interface 804 in FIG. 8Dprompts a user to hold device 800 near a pass reader terminal (e.g.,since pass 806 b has not been redeemed).

In some embodiments, device 800 displays pass 806 b (e.g., as part ofuser interface 804 in FIG. 8D) in response to receiving (e.g.,detecting) an input (e.g., after providing the prompt to provideauthorization for data corresponding to the second pass to be providedto pass reader terminal 850 by device 800). In some embodiments, theinput includes a contact on display 802, motion of device 800, and/orbiometric information (e.g. facial information, iris information,fingerprint information). In some embodiments, device 800 displays pass806 b (e.g., as part of user interface 804 in FIG. 8D) in response todetecting input 803 (e.g., a right-to-left swipe gesture on display 802)shown in FIG. 8C. In some embodiments, device 800 displays pass 806 b(e.g., as part of user interface 804 in FIG. 8D) after (e.g.,automatically after; without receiving further input; and/or in responseto) detecting that data corresponding to pass 806 a was provided bydevice 800 to pass reader terminal 850 (e.g., without having to receiveinput 803). In some embodiments, device 800 displays pass 806 b (e.g.,as part of user interface 804 in FIG. 8D) in response to detectingmotion of device 800 (e.g., raising and/or lowering of device 800;and/or raising and/or lowering of device 800 after detecting that datacorresponding to pass 806 a was provided by device 800 to pass readerterminal 850). In some embodiments, device 800 can display pass 806 b inresponse to receiving input (e.g., a right-to-left swipe gesture whiledisplaying pass 806 a) prior to (e.g., without) providing datacorresponding to pass 806 a to pass reader terminal 850 or detectingthat data corresponding to pass 806 a was provided by device 800 to passreader terminal 850. In some embodiments, in response to receiving(e.g., detecting) an input (e.g., a left-to-right swipe gesture ondisplay 802) while displaying pass 806 b (e.g., while displaying userinterface 804 as shown in FIG. 8D), device 800 displays pass 806 a(e.g., device 800 displays user interface 804 as shown in FIG. 8C).

In some embodiments, after (or while) displaying pass 806 b, device 800detects a request (e.g., placing device 800 next to pass reader terminal850) to provide authorization for data corresponding to pass 806 b topass reader terminal 850. FIG. 8E illustrates device 800 being held nearpass reader terminal 850 (e.g., while displaying pass 806 b). In FIG.8E, device 800 detects that data corresponding to pass 806 b wasprovided by device 800 to pass reader terminal 850. In some embodiments,the data corresponding to pass 806 b is provided via a signal from a NFCtransceiver, an optical scan, or a communication (e.g., a confirmationmessage from a remote server) indicating that a visual representation ofpass 806 b, such as a barcode or QR code, has been optically scanned.

After (e.g., in response to) detecting that data corresponding to pass806 b was provided by device 800 to pass reader terminal 850, device 800displays representation 806 b of the pass and an indication that datacorresponding to pass 806 b was provided by device 800 to pass readerterminal 850 (e.g., a checkmark icon and/or an animation of arepresentation of pass 806 b). In some embodiments, display 802 isdeactivated (e.g., off and/or in a sleep mode) before the data isprovided to pass reader terminal 850 (e.g., display 802 is activated(e.g., turned on) in response to detecting that data corresponding topass 806 b was provided by device 800 to pass reader terminal 850).

In the embodiment illustrated in FIG. 8E, the indication that datacorresponding to pass 806 b was provided by device 800 to pass readerterminal 850 includes displaying a check mark icon and displaying, onpass 806 b, stars (e.g., an animation of stars twinkling) and a revisedversion of the logo of the service provider on pass 806 a (e.g., ananimation of the whiskers and tail of the mouse moving). In someembodiments, after (e.g., in response to) detecting that datacorresponding to pass 806 b was provided by device 800 to pass readerterminal 850, device 800 provides a tactile and/or audible output, asindicated by the wavy lines around the corners of device 800 in FIG. 8E.In some embodiments, after (e.g., in response to) detecting that datacorresponding to pass 806 b was provided by device 800 to pass readerterminal 850, pass reader terminal 850 provides an indication (e.g.,audible output and/or a noise).

In some embodiments, in accordance with a determination that datacorresponding to a third pass is available to be provided to pass readerterminal 850 by device 800, device 800 provides a prompt (e.g., avisual, audible, and/or tactile prompt) to provide authorization fordata corresponding to the third pass to be provided to pass readerterminal 850 by device 800. In some embodiments, in accordance with thedetermination that data corresponding to a third pass is available to beprovided to pass reader terminal 850 by device 800, device 800 maintainsdisplay 802 in an active state (e.g., display 800 is turned on).

In some embodiments, pass 806 a, pass 806 b, and the third pass areassociated with each other (e.g., all three passes provide access to thesame event and/or day/time at the service provider). In someembodiments, other passes for a different event or time/day at theservice provider are not used (e.g., do not cause a prompt that datacorresponding to a third pass is available). In some embodiments, aprompt is provided only for additional passes that are associated withpass 806 b.

In some embodiments, providing the prompt includes displaying anindication that data corresponding to at least the third pass isavailable to be provided to pass reader terminal 850 by device 800(e.g., displaying paging dots, displaying a representation of a stack ofpasses, displaying an instruction to tap the screen, displaying aninstruction to swipe, displaying an instruction to tilt the phone,and/or displaying a portion of a second pass along an edge of thedisplay). In the embodiment illustrated in FIG. 8E, the prompt includesdisplaying the text “ADVANCE TO NEXT PASS” and displaying (e.g.,maintaining display of) indication 808 a. In some embodiments, theprompt indicates a number of passes available to be provided to the passreader terminal by device 800 (e.g., paging dots indication 808 a and/ora representation of a stack of passes indication 808 b). In someembodiments, providing the prompt includes outputting an audionotification that data corresponding to the third pass is available tobe provided to pass reader terminal 850 by device 800. In someembodiments, providing the prompt includes outputting, via one or moretactile output generators, a tactile output (e.g., vibration) when datacorresponding to the third pass is available to be provided to passreader terminal 850 by device 800.

In some embodiments, in accordance with a determination that datacorresponding to a third pass is not available to be provided to passreader terminal 850 by device 800, device 800 forgoes providing theprompt to provide authorization for data corresponding to a third passto be provided to pass reader terminal 850 by device 800. In someembodiments, in accordance with the determination that datacorresponding to a third pass is not available to be provided to passreader terminal 850 by device 800, device 800 deactivates display 802(e.g., display 802 is turned off and/or transitioned to a lower powerstate (e.g., a state with low brightness and/or refresh rate)).

In some embodiments, device 800 can display a representation of thethird pass and provide data corresponding to the third pass to passreader terminal 850 according to the same techniques described for pass806 a and pass 806 b with reference to FIGS. 8A-8F.

FIG. 8F illustrates an embodiment of user interface 804 including (e.g.,displaying) pass 806 a and indication 808 a (e.g., paging dots and/or astack of passes) showing that pass 806 a is one (e.g., the first) of aset of multiple (e.g., three) passes (e.g., the left paging dot ishighlighted and/or filled compared to the center dot and the right dot).In FIG. 8F, user interface 804 includes an indication 812 (e.g., aprompt) that all of the passes that are available to be provided to passreader terminal 850 by device 800 can be redeemed with an input (e.g., aparticular type of input and/or a press and hold gesture). In FIG. 8F,device 800 receives (e.g., detects) request 805 to redeem all passes(e.g., a press and hold gesture on display 802). In response toreceiving request 805, device 800 provides (e.g., automatically; withoutreceiving further input), to pass reader terminal 850, datacorresponding to all passes that are available to be provided to passreader terminal 850 by device 800 (e.g., data corresponding to pass 806a, pass 806 b, and/or a pass corresponding to the paging dot on theright side of indication 808 a).

In some embodiments, the techniques described with reference to FIGS.8A-8F can be applied to a set of passes that includes only one pass,only two passes, or more than three passes.

FIG. 9 is a flow diagram illustrating a method for providing a prompt toa user to provide authorization in accordance with some embodiments.Method 900 is performed at a computer system (e.g., 100, 300, 500, 600a, 600 b, 800) that is in communication with a display generationcomponent (e.g., 602 a, 602 b, 802) and one or more input devices (e.g.,a touch-sensitive surface). Some operations in method 900 are,optionally, combined, the orders of some operations are, optionally,changed, and some operations are, optionally, omitted.

As described below, method 900 provides an intuitive way for providing aprompt to a user to provide authorization for data corresponding to asecond pass to be provided to a pass reader terminal. The method reducesthe cognitive burden on a user when providing data corresponding to twoor more passes to a pass reader terminal, thereby creating a moreefficient human-machine interface. For battery-operated computingdevices, enabling a user to authenticate passes (e.g., grouped passes)faster and more efficiently conserves power and increases the timebetween battery charges.

In method 900, the computer system (e.g., 800) detects (902) (e.g., viaa signal from a NFC transceiver, an optical scan, and/or a communication(e.g., a confirmation message from a remote server) indicating that avisual representation of the pass such as a barcode or QR code has beenoptically scanned) that data corresponding to a first pass (e.g., 806 a)was provided by the computer system to a pass reader terminal (e.g.,850) that is separate from the computer system.

After detecting that data corresponding to the first pass was providedby the computer system to the pass reader terminal, the computer systemdisplays (904), via the display generation component (e.g., 802), anindication (e.g., 810, animation of pass 806 a) that data correspondingto the first pass was provided by the computer system to the pass readerterminal.

In accordance (906) with a determination that data corresponding to asecond pass (e.g., 806 b) is available to be provided to the pass readerterminal by the computer system, the computer system provides a prompt(e.g., 808 a, 810, a tactile notification, and/or an audio notification)to the user to provide authorization for data corresponding to thesecond pass to be provided to the pass reader terminal by the computersystem. In some embodiments, the first pass and second pass areassociated with each other (e.g., both passes provide access to the sameevent and/or day/time at the service provider (e.g., other passes for adifferent event or time/day at the service provider are not used and/ora prompt is provided only for additional passes that are associated withthe first pass). Providing a prompt to the user to provide authorizationfor data corresponding to a second pass to be provided to a pass readerterminal provides feedback to the user that an additional pass isavailable to be provided to the pass reader terminal. Providing improvedfeedback to the user enhances the operability of the computer system andmakes the user-system interface more efficient (e.g., by helping theuser to provide proper inputs and reducing user mistakes whenoperating/interacting with the computer system) which, additionally,reduces power usage and improves battery life of the computer system byenabling the user to use the computer system more quickly andefficiently.

In accordance (908) with a determination that data corresponding to asecond pass (e.g., 806 b) is not available to be provided to the passreader terminal by the computer system, the computer system forgoesproviding the prompt to the user to provide authorization for datacorresponding to a second pass to be provided to the pass readerterminal by the computer system.

In some embodiments, in response to detecting (e.g., via a NFC signalfrom the pass reader terminal, via a confirmation message from a remoteserver, and/or via an optical scan) that data corresponding to the firstpass was provided by the computer system to the pass reader terminal,the computer system displays, via the display generation component, auser interface (e.g., 804) including a representation of the first pass(e.g., 806 a) (e.g., an image with the name of a first guest and/or alogo for the service provider). In some embodiments, the display isdeactivated before the data is provided to the pass reader terminal.Displaying a user interface including a representation of the first passprovides visual feedback to the user confirming that a pass was providedto the pass reader terminal. Providing improved visual feedback to theuser enhances the operability of the computer system and makes theuser-system interface more efficient (e.g., by helping the user toprovide proper inputs and reducing user mistakes whenoperating/interacting with the computer system) which, additionally,reduces power usage and improves battery life of the computer system byenabling the user to use the computer system more quickly andefficiently.

In some embodiments, after displaying, via the display generationcomponent (e.g., 802), the indication (e.g., 810) that datacorresponding to the first pass (e.g., 806 a) was provided by thecomputer system to the pass reader terminal (e.g., 850), and inaccordance with the determination that data corresponding to a secondpass (e.g., 806 b) is available to be provided to the pass readerterminal by the computer system, the computer system maintains thedisplay generation component in an active state (e.g., the display isturned on). In some embodiments, in accordance with the determinationthat data corresponding to a second pass is not available to be providedto the pass reader terminal by the computer system, the computer systemdeactivates the display generation component (e.g., the display isturned off and/or transitioned to a lower power state (e.g., a statewith low brightness and/or refresh rate)). Maintaining the displaygeneration component in an active state in accordance with thedetermination that data corresponding to a second pass is available tobe provided to the pass reader terminal provides visual feedback to theuser that data corresponding to the second pass is available to beprovided to the pass reader terminal. Providing improved visual feedbackto the user enhances the operability of the computer system and makesthe user-system interface more efficient (e.g., by helping the user toprovide proper inputs and reducing user mistakes whenoperating/interacting with the computer system) which, additionally,reduces power usage and improves battery life of the computer system byenabling the user to use the computer system more quickly andefficiently.

In some embodiments, providing the prompt includes displaying, via thedisplay generation component, an indication (e.g., 808 a, 808 b, 810)that data corresponding to at least the second pass is available to beprovided to the pass reader terminal by the computer system (e.g.,displaying paging dots, displaying a representation of a stack ofpasses, displaying an instruction to tap the screen, displaying aninstruction to swipe, displaying an instruction to tilt the phone,and/or displaying a portion of a second pass along an edge of thedisplay). Displaying an indication that data corresponding to at leastthe second pass is available to be provided to the pass reader terminalby the computer system provides visual feedback to the user that anadditional pass is available to be provided to the pass reader terminal.Providing improved visual feedback to the user enhances the operabilityof the computer system and makes the user-system interface moreefficient (e.g., by helping the user to provide proper inputs andreducing user mistakes when operating/interacting with the computersystem) which, additionally, reduces power usage and improves batterylife of the computer system by enabling the user to use the computersystem more quickly and efficiently.

In some embodiments, the prompt indicates a number of passes availableto be provided to the pass reader terminal by the computer system (e.g.,808 a, 808 b) (e.g., paging dots and/or a representation of a stack ofpasses). Indicating a number of passes available to be provided to thepass reader terminal provides visual feedback to the user whether or notan additional pass is available to be provided to the pass readerterminal. Providing improved visual feedback to the user enhances theoperability of the computer system and makes the user-system interfacemore efficient (e.g., by helping the user to provide proper inputs andreducing user mistakes when operating/interacting with the computersystem) which, additionally, reduces power usage and improves batterylife of the computer system by enabling the user to use the computersystem more quickly and efficiently.

In some embodiments, providing the prompt includes outputting an audionotification that data corresponding to the second pass is available tobe provided to the pass reader terminal by the computer system.Outputting an audio notification that data corresponding to the secondpass is available to be provided to the pass reader terminal by thecomputer system provides feedback to the user that an additional pass isavailable to be provided to the pass reader terminal. Providing improvedfeedback to the user enhances the operability of the computer system andmakes the user-system interface more efficient (e.g., by helping theuser to provide proper inputs and reducing user mistakes whenoperating/interacting with the computer system) which, additionally,reduces power usage and improves battery life of the computer system byenabling the user to use the computer system more quickly andefficiently.

In some embodiments, providing the prompt includes outputting, via oneor more tactile output generators, a tactile output (e.g., vibration)when data corresponding to the second pass is available to be providedto the pass reader terminal by the computer system. Outputting a tactileoutput when data corresponding to the second pass is available to beprovided to the pass reader terminal by the computer system providesfeedback to the user that an additional pass is available to be providedto the pass reader terminal. Providing improved feedback to the userenhances the operability of the computer system and makes theuser-system interface more efficient (e.g., by helping the user toprovide proper inputs and reducing user mistakes whenoperating/interacting with the computer system) which, additionally,reduces power usage and improves battery life of the computer system byenabling the user to use the computer system more quickly andefficiently.

In some embodiments, after providing the prompt to the user to provideauthorization for data corresponding to the second pass to be providedto the pass reader terminal by the computer system, the computer systemdetects, via the one or more input devices, a user input (e.g., an inputon a touch-sensitive surface, motion of the computer system, and/orbiometric information (e.g. facial information, iris information, and/orfingerprint information)). In response to detecting the user input, thecomputer system displays, via the display generation component, arepresentation of the second pass (e.g., 806 b) (e.g., an image with thename of a second guest and/or a logo for the service provider). In someembodiments, after displaying the representation of the second pass, thecomputer system detects a request (e.g., placing the device next to apass reader) to provide authorization for data corresponding to thesecond pass to be provided to the pass reader). Displaying arepresentation of the second pass in response to detecting the userinput provides visual feedback to the user that data corresponding tothe second pass is available to be provided to the pass reader terminal.Providing improved visual feedback to the user enhances the operabilityof the computer system and makes the user-system interface moreefficient (e.g., by helping the user to provide proper inputs andreducing user mistakes when operating/interacting with the computersystem) which, additionally, reduces power usage and improves batterylife of the computer system by enabling the user to use the computersystem more quickly and efficiently.

In some embodiments, after providing the prompt to the user to provideauthorization for data corresponding to the second pass to be providedto the pass reader terminal by the computer system, the computer systemdetects authorization for data corresponding to the second pass to beprovided to the pass reader terminal by the computer system. In someembodiments, the authorization includes detecting motion (e.g., via anaccelerometer) of a component of the computer system from a loweredposition to a raised position (e.g., a device is lifted off the passreader to authorize the second pass). In some embodiments, theauthorization further includes detecting, via a biometric sensor (e.g.,camera and/or fingerprint sensor), biometric information (e.g., facialinformation, iris information, and/or fingerprint information). In someembodiments, after lifting the device off the pass reader, the device islowered again to provide the data corresponding to the second pass tothe pass reader. Authorizing data corresponding to the second pass to beprovided to the pass reader terminal by the computer system in responseto detecting motion of a component of the computer system from a loweredposition to a raised position allows a user to efficiently authorize thedata corresponding to the second pass to be provided to the pass readerterminal without having to provide extra inputs to navigate additionaluser interfaces. Reducing the number of user inputs needed to perform anoperation enhances the operability of the computer system and makes theuser-system interface more efficient (e.g., by helping the user toprovide proper inputs and reducing user mistakes whenoperating/interacting with the computer system) which, additionally,reduces power usage and improves battery life of the computer system byenabling the user to use the computer system more quickly andefficiently.

In some embodiments, the authorization for data corresponding to thesecond pass to be provided to the pass reader terminal includesdetecting a swipe gesture (e.g., 803) on the display generationcomponent. In some embodiments, after detecting the swipe gesture toauthorize the second pass, the data corresponding to the second pass isprovided to the pass reader. In some embodiments, the authorizationincludes detecting rotation of a rotatable input device (e.g., the crownof a watch). In some embodiments, the authorization further includesdetecting biometric information (e.g., facial information, irisinformation, and/or fingerprint information). Authorizing datacorresponding to the second pass to be provided to the pass readerterminal by the computer system in response to detecting a swipe gestureon the display generation component allows a user to efficientlyauthorize the data corresponding to the second pass to be provided tothe pass reader terminal without having to provide extra inputs tonavigate additional user interfaces. Reducing the number of user inputsneeded to perform an operation enhances the operability of the computersystem and makes the user-system interface more efficient (e.g., byhelping the user to provide proper inputs and reducing user mistakeswhen operating/interacting with the computer system) which,additionally, reduces power usage and improves battery life of thecomputer system by enabling the user to use the computer system morequickly and efficiently.

In some embodiments, the authorization for data corresponding to thesecond pass to be provided to the pass reader terminal includesdetecting, via the one or more input devices, an input (e.g., 805)(e.g., while the display generation component is in proximity to (e.g.,within range of a wireless signal from) the pass reader terminal) for apredetermined amount of time (e.g., a tap and hold gesture). In someembodiments, the input is on an icon indicating a group of passes can beprovided. In some embodiments, the input is at any location on thedisplay generation component. In some embodiments, detecting an input onthe display generation component for the predetermined amount of timeauthorizes data corresponding to all passes, including the first passand second pass, to be provided to the pass reader terminal. Authorizingdata corresponding to the second pass and one or more additional passesto be provided to the pass reader terminal by the computer system inresponse to detecting an input for a predetermined amount of time allowsa user to efficiently authorize the data corresponding to the secondpass and one or more additional passes to be provided to the pass readerterminal without having to provide extra inputs to navigate additionaluser interfaces. Reducing the number of user inputs needed to perform anoperation enhances the operability of the computer system and makes theuser-system interface more efficient (e.g., by helping the user toprovide proper inputs and reducing user mistakes whenoperating/interacting with the computer system) which, additionally,reduces power usage and improves battery life of the computer system byenabling the user to use the computer system more quickly andefficiently.

In some embodiments, prior to detecting that data corresponding to thefirst pass was provided by the computer system to the pass readerterminal, the computer system displays, via the display generationcomponent, a user interface (e.g., 804) including a representation ofthe first pass (e.g., 806 a) (e.g., an image with the name of a firstguest and/or a logo for the service provider). In some embodiments, therepresentation of the first pass is displayed in response to a userinput selecting the first pass. In some embodiments, the representationof the first pass is displayed in response to a user input causing datafor the first pass to be provided to the pass reader terminal.Displaying a user interface including a representation of the first passprovides visual feedback to the user that a pass is available to beprovided to the pass reader terminal. Providing improved visual feedbackto the user enhances the operability of the computer system and makesthe user-system interface more efficient (e.g., by helping the user toprovide proper inputs and reducing user mistakes whenoperating/interacting with the computer system) which, additionally,reduces power usage and improves battery life of the computer system byenabling the user to use the computer system more quickly andefficiently.

In some embodiments, data corresponding to the second pass (e.g., 806 b)is determined to be available to be provided to the pass reader terminalby the computer system when (e.g., only when) the first pass (e.g., 806a) and the second pass are associated with each other (e.g., both passesprovide access to the same event and/or day/time at the service provider(e.g., other passes for a different event and/or time/day at the serviceprovider are not used and/or a prompt is provided only for additionalpasses that are associated with the first pass)). Determining that datacorresponding to the second pass is available to be provided to the passreader terminal by the computer system when the first pass and thesecond pass are associated with each other provides additional controlto the user when redeeming passes (e.g., by prompting the user to redeemrelated passes and not passes for other venues or events). Providingadditional control of the computer system to the user enhances theoperability of the computer system and makes the user-system interfacemore efficient (e.g., by helping the user to provide proper inputs andreducing user mistakes when operating/interacting with the computersystem) which, additionally, reduces power usage and improves batterylife of the computer system by enabling the user to use the computersystem more quickly and efficiently.

Note that details of the processes described above with respect tomethod 900 (e.g., FIG. 9) are also applicable in an analogous manner tothe methods described below/above. For example, methods 700 and 1100optionally include one or more of the characteristics of the variousmethods described above with reference to method 900. For brevity, thesedetails are not repeated below.

FIGS. 10A-10L illustrate exemplary user interfaces for displaying amachine-readable code, in accordance with some embodiments. The userinterfaces in these figures are used to illustrate the processesdescribed below, including the processes in FIG. 11.

FIG. 10A illustrates device 1000, which includes display 1002 (e.g., atouchscreen display). In FIG. 10A, device 1000 displays user interface1004, which includes information about performing transactions with anaccount (e.g., a payment account, a bank account, a credit card account,a debit card account, and/or a data storage account). In someembodiments, user interface 1004 is a user interface for a vendorapplication (e.g., a third-party application associated with a bank,credit card, and/or data transfer service) or a vendor website (e.g., athird-party website associated with a bank, credit card, and/or datatransfer service).

User interface 1004 includes affordance 1006, which when selected,initiates a process for adding the account to a wallet application. Insome embodiments, the wallet application is a first-party applicationthat is developed, managed, and/or provided by the developer of device1000 and/or the operating system being run on device 1000. In FIG. 10A,while displaying user interface 1004, device 1000 receives (e.g.,detects) a request 1003 to add the account presented on user interface1004 to the first-party wallet application. In the embodimentillustrated in FIG. 10A, request 1003 includes a selection of (e.g., atap on) affordance 1006.

FIG. 10B illustrates device 1000 displaying user interface 1008 (e.g., auser interface for a wallet application). After (e.g., in response to)receiving request 1003 (as shown in FIG. 10A), user interface 1008includes a representation 1010 of the account (e.g., an image of acard), as shown in FIG. 10B. In some embodiments, while displaying userinterface 1008, device 1000 receives (e.g., detects) a request 1005 touse the account for a transaction. In the embodiment illustrated in FIG.10B, request 1005 includes a selection of (e.g., a tap on)representation 1010 of the account.

FIG. 10C illustrates device 1000 displaying user interface 1012, whichincludes representation 1010 of the account to be used for atransaction. In some embodiments, user interface 1012 is displayed inresponse to receiving (e.g., detecting) request 1005 to use the accountfor a transaction, as shown in FIG. 10B. In some embodiments, as shownin FIG. 10D, user interface 1012 further includes offer 1014 (e.g., aselectable offer). In some embodiments, offer 1014 is a discount thatcan be used for transactions performed with the account (e.g., offer1014 can be selected to obtain additional information about the offer,to access the offer, and/or to apply the offer).

In order to use the account for a transaction, the identity of a user ofdevice 1000 is authenticated. In some embodiments, the identity of theuser of device 1000 is authenticated using facial recognition. In someembodiments, facial recognition is initiated in response to receiving(e.g., detecting) a request 1001 to initiate facial recognition of theuser. In the embodiment illustrated in FIG. 10C, request 1001 includes adetecting a double click input (e.g., two presses within a predeterminedtime period) with button 1040. In some embodiments, the identity of theuser of device 1000 is authenticated using fingerprint recognition, apasscode, or other biometric information.

In accordance with a determination that the identity of the user ofdevice 1000 corresponds to an authorized user of the account, a firstmachine-readable code 1018 (e.g., a QR code and/or two-dimensional code)is displayed, as shown in FIG. 10E. In some embodiments, a secondmachine-readable code 1020 (e.g., a barcode and/or one-dimensional code)is displayed concurrently with first machine-readable code 1018. In someembodiments, displaying the first machine-readable code 1018 includesdisplaying an animation of the representation 1010 of the account (asshown in FIGS. 10C and 10D) transitioning to the first machine-readablecode 1018 (e.g., transitioning gradually between a plurality ofintermediate states while transitioning from the representation 1010 ofthe account to the machine-readable code 1018). In some embodiments,representation 1010 of the account is animated to appear to turn over sothat a back side 1016 of the representation is displayed (e.g., a cardimage is turned over), and the machine-readable code 1018 is included onthe back side 1016 of the representation (e.g., the back of the cardimage includes the machine-readable code).

In some embodiments, the first machine-readable code 1018 or secondmachine-readable code 1020 can be scanned (e.g., with a camera, laser,and/or other optical sensing device) to initiate a transaction using theaccount. For example, in some embodiments, the first machine-readablecode 1018 and second machine-readable code 1020 correspond to accountinformation (e.g., an account number). Using the account information,money can be transferred to or from the account. In some embodiments,the transaction is a transfer of money to a merchant to purchase goods.In some embodiments, the transaction is a person-to-person transfer ofmoney.

In some embodiments, the first machine-readable code 1018 and/or secondmachine-readable code 1020 is different each time the code is displayed(e.g., each time a request to use the account for a transaction isreceived and the identity of the user is determined to correspond to anauthorized user, a different code is displayed). This allows a uniquecode to be displayed for each transaction.

In FIG. 10E, while displaying the first machine-readable code 1018,device 1000 receives (e.g., detects) a request 1007 to display amachine-readable code at a larger size. In the embodiment illustrated inFIG. 10E, request 1007 includes a selection of (e.g., a tap on) the backside 1016 of the representation of the account. In response to detectingrequest 1007 to display a machine-readable code at a larger size, secondmachine-readable code 1020 is displayed at a larger size, as shown inFIG. 10F. In some embodiments, in response to detecting request 1007 todisplay a machine-readable code at a larger size, first machine-readablecode 1018 is displayed at a larger size. In some embodiments, displayinga machine-readable code at a larger size allows the machine-readablecode to be scanned more easily by a camera, laser, or other opticalsensing device.

In some embodiments, first machine-readable code 1018 and/or secondmachine-readable code 1020 ceases to be displayed after a predeterminedamount of time (e.g., 5 seconds, 15 seconds, 1 minute; and/or inresponse to a time threshold being met). In some embodiments, firstmachine-readable code 1018 and/or second machine-readable code 1020ceases to be displayed if no transaction confirmation is received withina predetermined amount of time (e.g., 5 seconds, 15 seconds, 1 minute;and/or in response to a time threshold being met). In some embodiments,the predetermined amount of time is an amount of time sinceauthenticating the user or since initially displaying themachine-readable code.

As shown in FIG. 10G, after ceasing to display first machine-readablecode 1018 and/or second machine-readable code 1020, a prompt isdisplayed to authenticate the identity of the user a second time. Insome embodiments, notification 1026 is displayed to indicate that notransaction confirmation is received. In some embodiments, ceasing todisplay first machine-readable code 1018 and/or second machine-readablecode 1020 includes replacing the display of first machine-readable code1018 and/or second machine-readable code 1020 with the display ofrepresentation 1010 of the account. In some embodiments, replacing thedisplay of first machine-readable code 1018 and/or secondmachine-readable code 1020 with the display of representation 1010 ofthe account includes displaying an animation of first machine-readablecode 1018 and/or second machine-readable code 1020 transitioning torepresentation 1010 of the account (e.g., transitioning graduallybetween a plurality of intermediate states while transitioning from themachine-readable code to the representation of the account). In someembodiments, back side 1016 of the representation (as shown in FIG. 10E)is animated to appear to turn over so that representation 1010 of theaccount is displayed (e.g., a card image is turned over from the backside to the front side).

In some embodiments, first machine-readable code 1018 and/or secondmachine-readable code 1020 is replaced with a different machine-readablecode after a predetermined amount of time (e.g., 5 seconds, 15 seconds,1 minute; and/or in response to a time threshold being met). In someembodiments, first machine-readable code 1018 and/or secondmachine-readable code 1020 is replaced with a different machine-readablecode if no transaction confirmation is received within a predeterminedamount of time (e.g., 5 seconds, 15 seconds, 1 minute; and/or inresponse to a time threshold being met). In some embodiments, thepredetermined amount of time is an amount of time since authenticatingthe user or since initially displaying the machine-readable code. Insome embodiments, the previously displayed machine-readable code becomesinvalid after a new machine-readable code is displayed.

As shown in FIG. 10H, after receiving a transaction confirmation (e.g.,from a third-party vendor application) that first machine-readable code1018 and/or second machine-readable code 1020 was successfully used toaccess information associated with the account (e.g., a transactionusing the account was approved), first machine-readable code 1018 and/orsecond machine-readable code 1020 ceases to be displayed and indication1030 (e.g., a checkmark) that information associated with the accountwas successfully accessed is displayed.

FIG. 10I illustrates device 1050, which includes display 1052 (e.g., atouchscreen display). In FIG. 10I, device 1000 displays user interface1054, which includes representation 1056 of an account to be used for atransaction (e.g., a payment account, a bank account, a credit cardaccount, a debit card account, and/or a data storage account). In FIG.10I, while displaying user interface 1054, device 1050 receives (e.g.,detects) request 1053 to use the account for a transaction. In theembodiment illustrated in FIG. 10I, request 1053 includes a selection of(e.g., a tap on) representation 1056 of the account.

In response to receiving (e.g., detecting) request 1053 to use theaccount for a transaction, first machine-readable code 1058 (e.g., a QRcode and/or two-dimensional code) is displayed, as shown in FIG. 10J. Insome embodiments, indication 1062 (e.g., paging dots) showing firstmachine-readable code 1058 is one (e.g., the first) of a set of multiple(e.g., two) types of machine-readable codes (e.g., the left paging dotis highlighted and/or filled compared to the right dot). In FIG. 10J,while displaying first machine-readable code 1058, device 1050 receives(e.g., detects) request 1055 to display a different type ofmachine-readable code. In the embodiment illustrated in FIG. 10J,request 1055 includes a swipe gesture on display 1052.

In response to receiving (e.g., detecting) request 1055 to display adifferent type of machine-readable code, second machine-readable code1060 (e.g., a barcode and/or one-dimensional code) is displayed, asshown in FIG. 10K. In some embodiments, indication 1062 is updated toindicate that a different type of machine-readable codes is beingdisplayed.

In some embodiments, the type of machine-readable code displayed inresponse to receiving (e.g., detecting) request 1053 to use the accountfor a transaction is based on the type of machine-readable code that waslast used for a transaction (e.g., if a barcode was last used for atransaction, then a barcode is displayed in response to request 1053instead of a QR code).

As shown in FIG. 10L, after receiving a transaction confirmation (e.g.,from a third-party vendor application) that first machine-readable code1058 and/or second machine-readable code 1060 was successfully used toaccess information associated with the account (e.g., a transactionusing the account was approved), first machine-readable code 1018 and/orsecond machine-readable code 1020 ceases to be displayed and indication1064 (e.g., a checkmark) that information associated with the accountwas successfully accessed is displayed.

FIG. 11 is a flow diagram illustrating a method for displaying amachine-readable code in response to receiving authentication data inaccordance with some embodiments. Method 1100 is performed at a computersystem (e.g., 100, 300, 500, 600 a, 600 b, 800, 1000, 1050) that is incommunication with a display generation component (e.g., 602 a, 602 b,802, 1002, 1052) and one or more input devices (e.g., a touch-sensitivesurface, a camera, a fingerprint sensor, and/or a biometric sensor).Some operations in method 1100 are, optionally, combined, the orders ofsome operations are, optionally, changed, and some operations are,optionally, omitted.

As described below, method 1100 provides an intuitive way for displayinga machine-readable code. The method reduces the cognitive burden on auser when displaying a machine-readable code with the computer system.For battery-operated computing systems, enabling a user to display amachine-readable code faster and more efficiently conserves power andincreases the time between battery charges.

In method 1100, the computer system (e.g., 1000, 1050) displays (1102),via the display generation component (e.g., 1002, 1052), a first userinterface (e.g., 1008, 1012, 1054) including an indication (e.g., 1010,1056) of an account (e.g., a payment card and/or a data storageaccount). In some embodiments, the first user interface is displayed inresponse to a double tap (e.g., 1001) of a hardware button (e.g., 1040).

The computer system receives (1104), via the one or more input devices(e.g., via one or more biometric sensors), authentication data (e.g.,facial information, fingerprint information, and/or a passcode).

In response (1106) to receiving the authentication data and inaccordance (1108) with a determination that the authentication datasatisfies authentication criteria associated with the account (e.g., thefacial information matches facial information of an account owner, thefingerprint information matches fingerprint information of an accountowner, and/or the passcode matches a passcode of an account owner), thecomputer system displays, via the display generation component, a firstmachine-readable code (e.g., 1018, 1020, 1058, 1060) (e.g., atwo-dimensional code (e.g., QR code) and/or a one-dimensional code(e.g., a barcode)) associated with the account (e.g., themachine-readable code can be used to authorize a transaction for theaccount). Displaying a machine-readable code in accordance with adetermination that the authentication data satisfies authenticationcriteria associated with the account provides visual feedback to theuser confirming that the authentication criteria are satisfied andimproves security of transactions using the machine-readable code.Providing improved visual feedback to the user enhances the operabilityof the computer system and makes the user-system interface moreefficient (e.g., by helping the user to provide proper inputs andreducing user mistakes when operating/interacting with the computersystem) which, additionally, reduces power usage and improves batterylife of the computer system by enabling the user to use the computersystem more quickly and efficiently.

In response (1106) to receiving the authentication data and inaccordance (1110) with a determination that the authentication data doesnot satisfy the authentication criteria associated with the account, thecomputer system forgoes display of the first machine-readable code(e.g., 1018, 1020, 1058, 1060) associated with the account.

In some embodiments, displaying the machine-readable code (e.g., 1018,1020, 1058, 1060) includes replacing the display of the indication(e.g., 1010, 1056) of the account with the display of themachine-readable code (e.g., ceasing display of the indication of theaccount and displaying the machine-readable code). In some embodiments,replacing the display of the indication of the account with the displayof the machine-readable code includes an animated transition from theindication of the account to the machine-readable code (e.g.,transitioning gradually between a plurality of intermediate states whiletransitioning from the indication of the account to the machine-readablecode). Replacing the display of the indication of the account with thedisplay of the machine-readable code provides visual feedback to theuser confirming that the authentication criteria are satisfied andimproves security of transactions using the machine-readable code.Providing improved visual feedback to the user enhances the operabilityof the computer system and makes the user-system interface moreefficient (e.g., by helping the user to provide proper inputs andreducing user mistakes when operating/interacting with the computersystem) which, additionally, reduces power usage and improves batterylife of the computer system by enabling the user to use the computersystem more quickly and efficiently.

In some embodiments, the computer system displays, via the displaygeneration component, a second user interface (e.g., 1004) for anapplication associated with a service provider (e.g., a third-partyapplication associated with a vendor (e.g., a bank and/or a merchant)).In some embodiments, the account is associated with the serviceprovider. In some embodiments, while displaying the second userinterface, the computer system detects a request (e.g., 1003) (e.g., viaa touch-sensitive surface) to configure the account for use in the firstuser interface (e.g., a request to add a card associated with the vendorto the first user interface) and, in response to detecting the requestto configure the account for use in the first user interface, thecomputer system includes the indication of the account in the first userinterface (e.g., 1008). Detecting a request to configure the account foruse in the first user interface while displaying the second userinterface allows a user to efficiently configure the account (e.g., foruse in a wallet application) without having to manually navigate betweenmultiple user interfaces. Reducing the number of inputs needed toperform an operation enhances the operability of the computer system andmakes the user-system interface more efficient (e.g., by helping theuser to provide proper inputs and reducing user mistakes whenoperating/interacting with the computer system) which, additionally,reduces power usage and improves battery life of the computer system byenabling the user to use the computer system more quickly andefficiently.

In some embodiments, the computer system receives, via the one or moreinput devices, second authentication data (e.g., facial information,fingerprint information, and/or a passcode), and, in response toreceiving the second authentication data and in accordance with adetermination that the second authentication data satisfies theauthentication criteria associated with the account (e.g., the facialinformation matches facial information of an account owner, thefingerprint information matches fingerprint information of an accountowner, and/or the passcode matches a passcode of an account owner), thecomputer system displays, via the display generation component, a secondmachine-readable code (e.g., 1018, 1020, 1058, 1060) (e.g., atwo-dimensional code (e.g., QR code) and/or a one-dimensional code(e.g., a barcode)) associated with the account, where the secondmachine-readable code is different from the first machine readable code(e.g., a different machine-readable code is displayed each time atransaction is authorized). In some embodiments, the machine-readablecode is different from all previous codes (e.g., the machine-readablecode is unique). In some embodiments, in response to receiving thesecond authentication data and in accordance with a determination thatthe second authentication data does not satisfy the authenticationcriteria associated with the account, the computer system forgoesdisplay of the second machine-readable code associated with the account.Displaying a second machine-readable code different from the firstmachine readable code provides visual feedback to the user confirmingthat the authentication criteria are satisfied and improves security oftransactions by using a different machine-readable code for eachtransaction. Providing improved visual feedback to the user enhances theoperability of the computer system and makes the user-system interfacemore efficient (e.g., by helping the user to provide proper inputs andreducing user mistakes when operating/interacting with the computersystem) which, additionally, reduces power usage and improves batterylife of the computer system by enabling the user to use the computersystem more quickly and efficiently.

In some embodiments, after displaying the machine-readable code (e.g.,1018, 1020, 1058, 1060) associated with the account, the computer systemceases to display the machine-readable code after a predetermined amountof time (e.g., 5 seconds, 15 seconds, 1 minute). In some embodiments,the computer system ceases to display the machine-readable code inresponse to a determination that a time threshold has been met (e.g.,the machine-readable code has been displayed for a predetermined amountof time and/or a predetermined amount of time has passed since receivingthe authentication information or since initially displaying themachine-readable code). Ceasing to display the machine-readable codeafter a predetermined amount of time improves security of transactionsby limiting the amount of time the machine-readable code is displayed.

In some embodiments, the machine-readable code is a firstmachine-readable code, and, after displaying the first machine-readablecode (e.g., 1018, 1020, 1058, 1060) associated with the account, thecomputer system ceases to display the first machine-readable code aftera predetermined amount of time (e.g., 5 seconds, 15 seconds, 1 minute;and/or in response to a time threshold being met) and the computersystem displays a second machine-readable code (e.g., 1018, 1020, 1058,1060) associated with the account that is different from the firstmachine-readable code associated with the account. In some embodiments,the second machine-readable code is displayed in response to a timethreshold being met (e.g., if the first machine-readable code has beendisplayed for a predetermined amount of time). Displaying a secondmachine-readable code different from the first machine readable codeimproves security of transactions by limiting the amount of time themachine-readable code is displayed.

In some embodiments, after displaying the machine-readable code (e.g.,1018, 1020, 1058, 1060) associated with the account, and in accordancewith (e.g., in response to) a determination that second authenticationdata is received within a predetermined amount of time (e.g., 5 seconds,30 seconds, 2 minutes; and/or in response to a time threshold being met)and the second authentication data satisfies authentication criteriaassociated with the account (e.g., the facial information matches facialinformation of an account owner, the fingerprint information matchesfingerprint information of an account owner, and/or the passcode matchesa passcode of an account owner), the computer system maintains displayof the machine-readable code associated with the account. In someembodiments, after displaying the machine-readable code associated withthe account and in accordance with (e.g., in response to) adetermination that second authentication data is not received within thepredetermined amount of time (e.g., 5 seconds, 30 seconds, 2 minutes;and/or in response to a time threshold being met) or the secondauthentication data does not satisfy the authentication criteriaassociated with the account, the computer system ceases to display themachine-readable code associated with the account. In some embodiments,the machine-readable code is replaced with a payment card image (e.g.,1010, 1056) (e.g., the card associated with the previously-displayedmachine-readable code). Ceasing to display the machine-readable code inaccordance with a determination that second authentication data is notreceived within the predetermined amount of time provides visualfeedback to the user that the authentication criteria were not satisfiedand also improves security of transactions by limiting the amount oftime the machine-readable code is displayed. Providing improved visualfeedback enhances the operability of the computer system and makes theuser-system interface more efficient (e.g., by helping the user toprovide proper inputs and reducing user mistakes whenoperating/interacting with the computer system) which, additionally,reduces power usage and improves battery life of the computer system byenabling the user to use the computer system more quickly andefficiently.

In some embodiments, after displaying the machine-readable code (e.g.,1018, 1020, 1058, 1060) associated with the account and in accordancewith (e.g., in response to) a determination that second authenticationdata is not received within the predetermined amount of time (e.g., 5seconds, 30 seconds, 2 minutes; and/or in response to a time thresholdbeing met) or the second authentication data does not satisfy theauthentication criteria associated with the account, the computer systemdisplays a request for the second authentication data (e.g., userinterface 1012 as shown in FIG. 10G) (e.g., a request to re-authorizethe transaction using biometric information (e.g., facial informationand/or fingerprint information) and/or a passcode). Displaying therequest for the second authentication data provides visual feedback tothe user that the second authentication data was not received within thepredetermined amount of time or that authentication criteria were notsatisfied. Providing improved visual feedback enhances the operabilityof the computer system and makes the user-system interface moreefficient (e.g., by helping the user to provide proper inputs andreducing user mistakes when operating/interacting with the computersystem) which, additionally, reduces power usage and improves batterylife of the computer system by enabling the user to use the computersystem more quickly and efficiently.

In some embodiments, after displaying the machine-readable code (e.g.,1018, 1020, 1058, 1060) associated with the account, the computer systemreceives a confirmation (e.g., from a third-party vendor app) that themachine-readable code was successfully used to access informationassociated with the account (e.g., a transaction using the account wasapproved), and, in response to receiving the confirmation that themachine-readable code was successfully used to access informationassociated with the account, the computer system ceases to display themachine-readable code and the computer system displays, via the displaygeneration component, an indication (e.g., 1030) that informationassociated with the account was successfully accessed (e.g., a checkmarkicon). Displaying an indication that information associated with theaccount was successfully accessed provides visual feedback to the userthat the machine-readable code was successfully used to accessinformation associated with the account. Providing improved visualfeedback enhances the operability of the computer system and makes theuser-system interface more efficient (e.g., by helping the user toprovide proper inputs and reducing user mistakes whenoperating/interacting with the computer system) which, additionally,reduces power usage and improves battery life of the computer system byenabling the user to use the computer system more quickly andefficiently.

In some embodiments, displaying the machine-readable code includesdisplaying the machine-readable code (e.g., 1020) at a first size. Insome embodiments, while displaying the machine-readable code at thefirst size, the computer system detects a request (e.g., 1007) (e.g., atap gesture on the machine-readable code) to display themachine-readable code at a larger size and, in response to detecting therequest to display the machine-readable code at a larger size, thecomputer system displays the machine-readable code at a second sizelarger than the first size (e.g., 1020 as shown in FIG. 10F). Displayingthe machine-readable code at a second size larger than the first sizeprovides additional control to the user over the size of themachine-readable code. A larger machine-readable code may improve theability of the code scanner to read the machine-readable code. Providingadditional control of the computer system to the user enhances theoperability of the computer system and makes the user-system interfacemore efficient (e.g., by helping the user to provide proper inputs andreducing user mistakes when operating/interacting with the computersystem) which, additionally, reduces power usage and improves batterylife of the computer system by enabling the user to use the computersystem more quickly and efficiently.

In some embodiments, the machine-readable code is a machine readablecode of a first type (e.g., 1058) (e.g., a QR code). In someembodiments, while displaying the machine-readable code of the firsttype, the computer system detects a request (e.g., 1055) (e.g., a swipegesture) to display a machine-readable code of a second type (e.g.,1060) (e.g., a barcode) and in response to detecting the request todisplay the machine-readable code of the second type, the computersystem displays the machine-readable code of the second type (e.g., a QRcode is replaced with a barcode and/or a barcode is replaced with a QRcode). In some embodiments, e.g., on a watch (e.g., 1050), the requestto display the second type of machine-readable code is detected aftertapping on a representation (1056) of the account to display themachine-readable code. In some embodiments, the order of display of QRcode or barcode is based on the type of code that was displayed mostrecently. Displaying a machine-readable code of the second type providesadditional control to the user over the type of machine-readable code. Adifferent type of machine-readable code may allow the machine-readablecode to be scanned by additional types of code scanners. Providingadditional control of the computer system to the user enhances theoperability of the computer system and makes the user-system interfacemore efficient (e.g., by helping the user to provide proper inputs andreducing user mistakes when operating/interacting with the computersystem) which, additionally, reduces power usage and improves batterylife of the computer system by enabling the user to use the computersystem more quickly and efficiently.

In some embodiments, displaying the first user interface includesdisplaying one or more offers (e.g., 1014; a selectable offer)associated with the account (e.g., a discount that can be used fortransactions with the account provider). Displaying one or more offersassociated with the account allows the user to access contextuallyrelevant offers from the first user interface without having to navigateto additional user interfaces. Reducing the number of inputs needed toperform an operation enhances the operability of the computer system andmakes the user-system interface more efficient (e.g., by helping theuser to provide proper inputs and reducing user mistakes whenoperating/interacting with the computer system) which, additionally,reduces power usage and improves battery life of the computer system byenabling the user to use the computer system more quickly andefficiently.

Note that details of the processes described above with respect tomethod 1100 (e.g., FIG. 11) are also applicable in an analogous mannerto the methods described above. For example, methods 700 and 900optionally include one or more of the characteristics of the variousmethods described above with reference to method 1100. For brevity,these details are not repeated below.

FIG. 12A illustrates an electronic device 1200 with display 1202 (e.g.,touch screen) and one or more input devices (e.g., rotatable inputmechanism 1204, side button 1206). At FIG. 12A, electronic device 1200displays, on display 1202, account user interface 1208 (e.g., similar toaccount user interface 1302 described below with reference to FIG. 13B).Electronic device 1200 displays a plurality of platters 1210 associatedwith respective computer storage accounts of a user on account userinterface 1208. The respective computer storage accounts of the userinclude varying amounts of (e.g., cloud-based) computer storageresources. In some embodiments, different types of data (e.g., datacorresponding to photo files, data corresponding to document files, datacorresponding to music files, data corresponding to video files, and/ordata corresponding to application files) can be stored and/or archivedin the computer storage resources associated with the computer storageaccounts. Accordingly, in response to detecting user input correspondingto a selection of a platter of the plurality of platters 1210,electronic device 1200 displays information related to the computerstorage resources (e.g., amount of data available and/or amount of dataconsumed) associated with the respective computer storage accountcorresponding to the selected platter.

At FIG. 12A, electronic device 1200 displays storage card platter 1210 aand memory platter 1210 b (e.g., a partial view of memory computerstorage account platter 1210 b) on account user interface 1208. Further,at FIG. 12A, electronic device 1200 detects swipe gesture 1250 a (e.g.,upward swipe gesture). In response to detecting swipe gesture 1250 a,electronic device 1200 scrolls account user interface 1208 (e.g.,scrolls and/or translates the plurality of platters 1210 of the accountuser interface 1208 in a downward direction) to display additionalplatters of the plurality of platters 1210. In some embodiments,electronic device 1200 is also configured to scroll account userinterface 1208 based on rotation of rotatable input mechanism 1204 inaddition to swipe gestures.

For instance, at FIG. 12B, electronic device 1200 displays storage cardplatter 1210 a (e.g., a partial view of storage card platter 1210 a),memory platter 1210 b, and shared data platter 1210 c (e.g., a partialview of shared data platter 1210 c) on account user interface 1208. Assuch, swipe gesture 1250 a causes additional platters of the pluralityof platters 1210 (e.g., shared data platter 1210 c) to be at leastpartially displayed on account user interface 1208.

At FIG. 12C, electronic device 1200 has detected the end of swipegesture 1250 a and electronic device 1200 is displaying account userinterface 1208 while memory platter 1210 b is in a center of display1202 (e.g., memory platter 1250 a has stopped scrolling and/orelectronic device 1200 does not detect any further user inputs to scrollthe platters after swipe gesture 1250 a causes scrolling of account userinterface 1208). As a result of pausing on memory platter 1210 b (e.g.,displaying memory player 1210 b at a predefined location (or within apredefined area) of the display or user interface for at least apredetermined period of time (e.g., without scrolling memory platter1210 b during the duration of the predetermined period of time)),account user interface 1208 is modified, as shown at FIG. 12C.

At FIG. 12C, appearances of storage card platter 1210 a and shared dataplatter 1210 c are deemphasized when compared to memory platter 1210 b.Storage card platter 1210 a and shared data platter 1210 c aredeemphasized by being reduced in size when compared to memory platter1210 b. To further deemphasize the platters, an appearance of storagecard platter 1210 a and an appearance of shared data platter 1210 c arealtered (e.g., reduced in opacity, blurred, and/or modified in color)when compared to memory platter 1210 b (e.g., as represented at FIG. 12Cby hatching). In some embodiments, electronic device 1200 is configuredto deemphasize the platters by ceasing to display platters that are notpositioned in the center of display 1202.

Additionally, in some embodiments, as a result of pausing on memoryplatter 1250 a, account user interface 1208 updates to include indicator1212 (“Tap to View”) indicating a prompt to a user of electronic device1200 to view additional details related to the computer storage accountassociated with and/or represented by memory platter 1210 b. In responseto detecting a tap gesture on memory platter 1210 b, electronic device1200 displays a details user interface that provides the user withvisual representations related to the computer storage resources of thecomputer storage account associated with memory platter 1210 b. In someembodiments, electronic device 1200 forgoes display of the indicator1212 on account user interface 1208 based on the user inputs that causeddisplay of account user interface 1208, as discussed in detail belowwith reference to FIGS. 13A-13N. In some embodiments, a tap gesture onmemory platter 1210 b causes display of the details user interfaceregardless of whether or not indicator 1212 is displayed on account userinterface 1208.

FIG. 13A illustrates electronic device 1200 displaying user interface1300. At FIG. 13A, user interface 1300 is a watch face. In otherembodiments, user interface 1300 is user interface associated with anapplication of electronic device 1200. At FIG. 13A, electronic device1200 detects user input 1350 a (e.g., a double press gesture and/ordouble tap gesture) on side button 1206. In response to detecting userinput 1350 a, electronic device 1200 displays account user interface1302 of a transfer application (e.g., an electronic wallet application),as shown at FIG. 13B. Further, at FIG. 13A, electronic device 1200detects user input 1350 b (e.g., a single press and/or single tap input)on crown 1204. In response to detecting user input 1350 b, electronicdevice 1200 displays application user interface 1320, as shown at FIG.13I. In some embodiments, electronic device 1200 displays account userinterface 1302 in response to detecting user input 1350 a (e.g., adouble press gesture and/or double tap gesture) regardless of what isbeing displayed on display 1202 (e.g., watch face user interface 1300,user interface of another application, and/or application user interface1320).

As discussed in detail below with reference to FIGS. 13B-13N, user input1350 a authorizes and/or activates transfer accounts linked toelectronic device 1200. As such, electronic device 1200 releases (e.g.,transmits) credentials associated with a respective transfer accountwhen a set of transfer criteria is met (e.g., when electronic device1200 is positioned within a threshold proximity of a receiver and thelinked transfer account is authorized/activated). In contrast, receivinga different set of user inputs (e.g., user input 1350 b followed by tapgesture 1350 h at FIG. 13I) causes electronic device 1200 to displayaccount user interface 1302 without authorizing and/or activatingtransfer accounts linked to electronic device 1200 (without further userinput). As such, in response to detecting user input 1350 b (anddetecting tap gesture 1350 h) electronic device 1200 does not releasecredentials associated with the respective transfer account when the setof transfer criteria is met.

At FIG. 13B, account user interface 1302 includes a plurality ofplatters 1304 associated with respective transfer accounts (e.g.,payment accounts, such as a third-party credit card account, a debitcard account, and/or a stored-value account; pass accounts; ticketaccounts; point accounts; rewards accounts; and/or transit accounts)linked to (e.g., provisioned onto) electronic device 1200. In someembodiments, a user can provision electronic device 1200 with one ormore transfer accounts and use the transfer accounts to conducttransfers. For example, upon receiving access to the transfer account ofa user, electronic device 1200 receives and stores credentialsassociated with the transfer account (e.g., account numbers, pin codes,authorization codes, pass codes, card number, balance information,and/or address) in a secure element of electronic device 1200.Electronic device 1200 releases (e.g., transmits) the credentialsassociated with the transfer account to a terminal (e.g., a wirelesscommunication terminal and/or an NFC terminal) when the transfer accountis activated and/or authorized by the user (e.g., via user input 1350a).

At FIG. 13B, electronic device 1200 displays transfer card platter 1304a representing a first transfer account (e.g., a credit card account, adebit card account, and/or a dual credit/debit card account) and cashplatter 1304 b (e.g., a partial view of cash platter 1304 b)representing a second transfer account (e.g., a cash card and/or a giftcard) on account user interface 1302. At FIG. 13B, transfer card platter1304 a and cash platter 1304 b have the same emphasis (e.g., sameopacity, same size, and/or same height). Although transfer card platter1304 a is displayed in the center of display 1202 (e.g., at a predefinedlocation (or within a predefined area) of the display or userinterface), electronic device 1202 does not change the emphasis of(e.g., deemphasize) cash platter 1304 b with respect to transfer cardplatter 1304 a because electronic device 1202 has not paused on transfercard platter 1304 a (e.g., electronic device 1202 has not displayedtransfer card platter 1304 a at the predefined location (or within thepredefined area) of the display or user interface for at least apredetermined period of time (e.g., without scrolling transfer cardplatter 1304 a during the predetermined period of time)).

At FIG. 13B, electronic device 1200 detects swipe gesture 1350 c (e.g.,an upward swipe gesture) before the duration of the predetermined periodof time passes. In response to detecting swipe gesture 1350 c,electronic device 1200 scrolls account user interface 1302 (e.g.,scrolls and/or translates the plurality of platters 1304 of account userinterface 1302 in an upward direction) to display additional platters(e.g., 1304 c, 1304 d) of the plurality of platters 1304, as shown inFIG. 13C. In some embodiments, electronic device 1200 is also configuredto scroll account user interface 1208 based on rotation of rotatableinput mechanism 1204 in addition to swipe gestures.

At FIG. 13C, electronic device 1200 displays cash platter 1304 b (e.g.,a partial view of cash platter 1304 b) representing the second transferaccount, boarding pass platter 1304 c representing a third transferaccount (e.g., an airlines account), and loyalty card platter 1304 d(e.g., a partial view of loyalty card platter 1304 d) representing afourth transfer account (e.g., a loyalty account and/or a rewardsaccount) on account user interface 1302. As such, swipe gesture 1350 ccauses additional platters of the plurality of platters 1304 (e.g.,boarding pass platter 1304 c and/or loyalty card platter 1304 d) to beat least partially displayed on account user interface 1302.

At FIG. 13C, while the platters have stopped scrolling and arestationary. Although boarding pass platter 1304 c is displayed in thecenter of display 1202 (e.g., at the predefined location (or within thepredefined area) of the display or user interface), electronic device1202 does not change the emphasis of (e.g., deemphasize) platters 1304 band 1304 d with respect to boarding pass platter 1304 c becauseelectronic device 1202 has not paused on boarding pass platter 1304 c(e.g., electronic device 1202 has not displayed boarding pass platter1304 c at the predefined location (or within the predefined area) of thedisplay or user interface for at least the predetermined period of time(e.g., without scrolling boarding pass platter 1304 c during thepredetermined period of time)).

At FIG. 13C (and before the predetermined period of time passes),electronic device 1200 detects swipe gesture 1350 d (e.g., a downwardswipe gesture) on account user interface 1302. In response to detectingswipe gesture 1350 d, electronic device 1200 scrolls account userinterface 1302 (e.g., scrolls and/or translates the plurality ofplatters 1304 of account user interface 1302 in an upward direction) todisplay account user interface 1302 as shown at FIG. 13D. At FIG. 13D,after swipe gesture 1350 d ceases, electronic device 1200 stopsscrolling account user interface 1302 (e.g., 3 seconds after detectingan end of swipe gesture 1350 d) and electronic device 1200 pauses ontransfer card platter 1304 a (e.g., transfer card platter 1304 a isdisplayed in the center of display 1202 (e.g., at the predefinedlocation (or within the predefined area) of the display or userinterface) for at least the predetermined period of time (e.g., withoutscrolling transfer card platter 1304 a during the predetermined periodof time)). As a result of pausing on transfer card platter 1304 a (forthe predetermined period of time (e.g., half a second, one second, twoseconds)), account user interface 1302 is modified, as shown at FIG.13D. In some embodiments, prior to pausing on a particular platter, eachplatter of the plurality of platters includes a uniform size (e.g., eachplatter includes the same size and/or shape). In some embodiments, priorto pausing on a particular platter, the platters of the plurality ofplatters have different heights, sizes, and/or shapes.

At FIG. 13D, as a result of pausing on transfer card platter 1304 a,(regardless of whether the platters had a uniform or non-uniformappearance in FIG. 13C) an appearance of cash platter 1304 b isdeemphasized as compared to transfer card platter 1304 a. Deemphasizingcash platter 1304 b as compared to transfer card platter 1304 aincludes, for example, reducing the size of cash platter 1304 b ascompared to transfer card platter 1304 a (e.g., reducing size of cashplatter 1304 b without reducing (or with increasing) the size oftransfer card platter 1304 a and/or increasing the size of transfer cardplatter 1304 a without increasing (or with reducing) the size of cashplatter 1304 b). Further, an additional appearance of cash platter 1304b is optionally altered (e.g., reduced in opacity, blurred, and/ormodified in color) as compared to transfer card platter 1304 a (e.g., asrepresented at FIG. 13D by hatching of cash platter 1304 b) todeemphasize cash platter 1304 b. In some embodiments, electronic device1200 is configured to deemphasize platters that are not positioned inthe center of display 1202 (e.g., cash platter 1304 b) by ceasing todisplay the platters.

Additionally, at FIG. 13D, as a result of pausing on transfer cardplatter 1304 a and because the user input that caused display of accountuser interface 1302 was user input 1350 a (and not tap gesture 1350 h),electronic device 1200 displays indicator 1306 (“Hold Near Reader”)indicating that a transfer account (e.g., the first transfer account)associated with transfer card platter 1304 a is activated (e.g.,authorized for use to conduct a transfer and/or transaction). Indicator1306 prompts a user of electronic device 1200 to position electronicdevice proximate to a receiver (e.g., within a threshold proximity of adevice capable of receiving transmissions from electronic device 1200).Accordingly, once electronic device 1200 is positioned within proximityof the receiver (e.g., within proximity of a wireless communicationterminal) the transfer account associated with transfer card platter1304 a can be utilized to conduct a transfer (e.g., a transaction usingmonetary funds, a transfer of points, a transfer of credit, and/orauthorization of entry) without further user input. User input 1350 a(as compared to tap gesture 1350 h) that causes electronic device 1200to display account user interface 1302 also enables electronic device1200 to authorize the transfer accounts associated with the plurality ofplatters 1304 of account user interface 1302. As discussed below withreference to FIGS. 13I-13K, accessing account user interface 1302 via atechnique that does not include user input 1350 a (e.g., insteadincludes tap gesture 1350 h and/or a voice instruction), does notactivate the transfer account associated with transfer card platter 1304a when pausing on transfer card platter 1304 a in account user interface1302.

At FIG. 13D, electronic device 1200 detects swipe gesture 1350 e (e.g.,upward swipe gesture). In response to detecting swipe gesture 1350 e,electronic device 1200 optionally undoes the deemphasizing (e.g.,returns the platters to the visual appearance before the deemphasizing)and scrolls account user interface 1302 (e.g., scrolls and/or translatesthe plurality of platters 1304 of account user interface 1302 in adownward direction) to display cash platter 1304 b, boarding passplatter 1304 c, and loyalty card platter 1304 d, as shown at FIG. 13E.Alternatively to detecting swipe gesture 1350 e, electronic device 1200detects tap gesture 1350 f on transfer card platter 1304 a. In responseto detecting tap gesture 1350 f, electronic device 1200 displays detailsuser interface 1330, as shown at FIG. 13O.

At FIG. 13E, in response to detecting swipe gesture 1350 e, electronicdevice 1200 displays account user interface 1302 and pauses account userinterface 1302 on boarding pass platter 1304 c. As a result of pausingon boarding pass platter 1304 c (for the predetermined period of time(e.g., half a second, one second, two seconds)), account user interface1302 is modified, as shown at FIG. 13E.

At FIG. 13E, in response to pausing on boarding pass platter 1304 c, anappearance of cash platter 1304 b and an appearance of loyalty cardplatter 1304 d are deemphasized as compared to boarding pass platter1304 c. Deemphasizing optionally includes cash platter 1304 b andloyalty card platter 1304 d being reduced in size when compared toboarding pass platter 1304 c. Further, the deemphasizing optionallyincludes an appearance of cash platter 1304 b and an appearance ofloyalty card platter 1304 d being altered (e.g., reduced in opacity,blurred, and/or modified in color) as compared to boarding pass platter1304 c (e.g., as represented at FIG. 13E by hatching of cash platter1304 b and loyalty card platter 1304 d).

Additionally, at FIG. 13E, in response to pausing on boarding passplatter 1304 c, electronic device 1200 displays indicator 1308 (“Tap toView Code”) indicating that a transfer account (e.g., the third transferaccount) associated with boarding pass platter 1304 c is authorizedand/or activated (e.g., boarding pass is authorized for scanning). AtFIG. 13E, boarding pass platter 1304 c includes display of visualindicators of information related to a particular pass represented byboarding pass platter 1304 c. For example, boarding pass platter 1304 cincludes display of visual indications that distinguish boarding passplatter 1304 c from other boarding pass platters of the plurality ofplatters 1304. Boarding pass platter 1304 c displays visual indicationsof a name of a passenger associated with boarding pass platter 1304 c(“John Appleseed”), a date of travel (e.g., a flight) associated withboarding pass platter 1304 c (“Feb. 3, 2020”), airline information ofthe flight associated with boarding pass platter 1304 c (“AIRLINE”),and/or flight information of the flight associated with boarding passplatter (“SFO DEN”, start location and destination). Accordingly,electronic device 1200 enables a user to easily avoid confusingdifferent passes (e.g., boarding passes) that have a similar appearanceon account user interface 1302 based on the displayed detailsrepresented by visual indications on boarding pass platter 1304 c.

At FIG. 13E, while boarding pass platter 1304 c is authorized and/oractivated (as visually indicated by the other platters being relativelydeemphasized), electronic device 1200 detects tap gesture 1350 g onboarding pass platter 1304 c. In response to detecting tap gesture 1304c, electronic device 1200 displays machine-readable code 1310 (e.g., aQR code and/or a bar code), as shown at FIG. 13G. In order to displaycode 1310 at FIG. 13G, electronic device 1200 displays a transition(e.g., an animation) between account user interface 1302 at FIG. 13E andcode 1310 at FIG. 13G. For instance, at FIG. 13F, electronic device 1200displays boarding pass details user interface 1326 in response to tapgesture 1350 g. In some embodiments, boarding pass details userinterface 1326 includes additional information related to the transferaccount associated with boarding pass platter 1304 c (e.g., flightdetails). In some embodiments, electronic device 1200 displays boardingpass details user interface 1326 as an animation before displaying code1310 as shown at FIG. 13G (e.g., electronic device 1200 displaysboarding pass details user interface 1326 and then scrolls the boardingpass details user interface 1326 to display code 1310 as a continuoussequence in response to tap gesture 1350 g).

At FIG. 13G, electronic device 1200 displays code 1310 in a full screenmode (e.g., code 1310 occupies greater than 80% of display 1202, greaterthan 85% of display 1202, greater than 90% of display 1202, and/orgreater than 95% of display 1202) in response to tap gesture 1350 g. Insome embodiments, electronic device 1200 increases a brightness ofdisplay 1202 (e.g., brightness output of display 1202) in the fullscreen mode. In some embodiments, electronic device 1200 displaysindicator 1314 (“Scan Code”) prompting the user to position electronicdevice 1200 proximate to a reader (e.g., a device that receivestransmissions of credentials from electronic device 1200), such thatcode 1310 may be scanned (e.g., to authorize a user to board a plane).In some embodiments, electronic device 1200 forgoes display of indicator1314, thereby enabling a size of code 1310 to further increase ondisplay 1202. Accordingly, the transfer account associated with boardingpass platter 1304 c can be utilized in response to user input 1350 a andtap gesture 1350 g. As discussed below, a tap gesture on boarding passplatter 1304 c after accessing account user interface 1302 via userinput 1350 b does not automatically display code 1310 in the full screenmode. Rather, as discussed below, electronic device 1200 detects furtheruser input to display code 1310 in a center position of display 1202(e.g., further user input is required for electronic device 1200 todisplay code 1310 for scanning). In some embodiments, detecting userinput (e.g., a swipe gesture and/or rotation of rotatable inputmechanism 1204) when electronic device 1200 displays code 1310 in thefull screen mode causes electronic device 1200 to scroll the userinterface to display additional details related to the transfer accountassociated with boarding pass platter 1304 c (e.g., as shown at FIG.13N) (and to optionally cease displaying code 1310 in the full screemode).

At FIG. 13H, electronic device 1200 has paused user interface account1302 on second cash platter 1304 e. As a result of pausing on secondcash platter 1304 e, account user interface 1302 is modified, as shownat FIG. 13H. In particular, an appearance of loyalty card platter 1304 dand an appearance of transit platter 1304 f are deemphasized as comparedto second cash platter 1304 d (e.g., sizes of loyalty card platter 1304d and transit platter 1304 f are reduced, appearances of loyalty cardplatter 1304 d and transit platter 1304 f are reduced in opacity, areblurred, and/or are changed in color).

At FIG. 13H, electronic device 1200 displays indicator 1316 (overlaid onanother platter) having an error message indicating that a transferaccount (e.g., the fifth transfer account) associated with second cashplatter 1304 d is unavailable. In some embodiments, electronic device1200 displays the error message when account user interface 1302 isaccessed via user input 1350 a and electronic device 1200 detects thatthe transfer account associated with second cash platter 1304 d cannotcomplete a transfer and/or that electronic device 1200 cannot otherwiseaccess the transfer account. For instance, electronic device 1200displays the error message when a transfer account associated with aplatter of the plurality of platters 1304 cannot be accessed byelectronic device 1200 and/or includes insufficient transfer credits(e.g., monetary funds, credits, and/or points) to complete a transfer.

As set forth above, account user interface 1302 can be accessed viaother user inputs detected by electronic device 1200. For example, atFIG. 13I, electronic device 1200 displays application user interface1320 in response to detecting user input 1350 b at FIG. 13A. At FIG.13I, application user interface 1320 includes a plurality of applicationuser interface objects 1322 corresponding to applications of electronicdevice 1200. Further, at FIG. 13I, electronic device 1200 detects tapgesture 1350 h on transfer application user interface object 1322 a. Inresponse to detecting tap gesture 1350 h, electronic device 1200displays account user interface 1302, as shown at FIG. 13J. As notedabove, accessing account user interface 1302 via tap gesture 1350 h doesnot authorize and/or authenticate transfer accounts of the transferapplication. As such, additional user input is detected by electronicdevice 1200 for a respective transfer account of the transferapplication to be utilized to conduct a transfer.

At FIG. 13J, electronic device 1200 displays account user interface 1302having the plurality of platters 1304. Electronic device 1200 displaystransfer card platter 1304 a and cash platter 1304 b on account userinterface 1302. In some embodiments, electronic device 1200 does notdetect user input after detecting tap gesture 1350 h, such thatelectronic device 1200 pauses account user interface 1302 on transfercard platter 1304 a. Accordingly, in response to detecting that accountuser interface 1302 is paused on transfer card platter 1304 a (for thepredetermined period of time (e.g., half of a second, one second, twoseconds)), electronic device 1200 modifies account user interface 1302,as shown at FIG. 13K.

At FIG. 13K, cash platter 1304 b is deemphasized in appearance (e.g.,reduced in size, reduced in opacity, blurred, and/or changed in color)as compared to transfer card platter 1304 a. Because user input 1304 band tap gesture 1350 h do not authorize transfer accounts of thetransfer application, at FIG. 13K, account user interface 1302 includesindicator 1324 (“Double Click to Pay”) prompting a user to authorizeand/or activate the transfer account associated with transfer cardplatter 1304 a. In some embodiments, electronic device 1200 detects userinput (e.g., a double press gesture and/or a double tap gesture) on sidebutton 1206. In response to the user input, electronic device 1200authorizes and/or activates the transfer account associated with platter1304 a, such that a user can position electronic device 1200 within athreshold proximity of a receiver (e.g., within proximity of a wirelesscommunication terminal) to release (e.g., transmit) credentials of thetransfer account to conduct a transfer.

At FIG. 13K, electronic device detects swipe gesture 1350 i (e.g.,upward swipe gesture) on account user interface 1302. In response todetecting swipe gesture 1350 i, electronic device 1200 scrolls accountuser interface 1302 to show additional platters of the plurality ofplatters 1304 (e.g., scrolls and/or translates the plurality of platters1304 of account user interface 1302 in the upward direction to displayadditional platters), as shown at FIG. 13L. Alternatively, electronicdevice detects tap gesture 1350 j on transfer card platter 1304 a. Inresponse to detecting tap gesture 1350 j, electronic device 1200displays details user interface 1330, as shown at FIG. 13O.

At FIG. 13L, user interface 1302 has stopped scrolling and electronicdevice 1200 pauses display of account user interface 1302 on boardingpass platter 1304 c (e.g., in a center of display 1202 for at least thepredetermined period of time (e.g., half a second, one second, twoseconds)). In response to pausing on boarding pass platter 1304 c,electronic device 1200 modifies account user interface 1302 todeemphasize appearances of cash platter 1304 b and loyalty card platter1304 d (e.g., reduces sizes, reduces opacities, blurs, and/or changescolors of cash platter 1304 b and loyalty card platter 1304 d) ascompared to boarding pass platter 1304 c, as shown in FIG. 13L.

As set forth above, accessing account user interface 1302 via tapgesture 1350 h does not activate and/or authorize transfer accounts oftransfer application. At FIG. 13L, while boarding pass platter 1304 c isemphasized, electronic device 1200 detects tap gesture 1350 k onboarding pass platter 1304 c. Instead of displaying boarding passdetails user interface 1326 and automatically displaying code 1310 inthe full screen mode as described with respect to FIGS. 13E-13G,electronic device 1200 displays (in response to detecting tap gesture1350 k) boarding pass details user interface 1326 without automaticallydisplaying code 1310 in the full screen mode, as shown at FIG. 13M,because account user interface 1302 was displayed in response to tapgesture 1350 h.

In response to detecting tap gesture 1350 k, at FIG. 13M, electronicdevice 1200 displays boarding pass details user interface 1326, whichincludes boarding pass platter 1304 c, details indicator 1326 a (e.g.,an indication that the traveler associated with boarding pass ofboarding pass platter 1304 c is a checked traveler, has a particularstatus, and/or has a particular security clearance), and a partial(incomplete) view of machine-readable code 1310 (e.g., QR code and/orbar code) (e.g., including a first part of code 1310, not including asecond part of code 1310). The partial view of machine-readable code1310 is incomplete and does not permit the full machine-readable code1310 to be read be a reader. Electronic device 1200 forgoes automaticdisplay of code 1310 in the full screen mode in response to detectingtap gesture 1350 k. Thus, to activate and/or authenticate code 1310,electronic device 1200 detects swipe gesture 1350 l (e.g., upward swipegesture), as shown at FIG. 13M.

In response to detecting swipe gesture 1350 l, electronic device 1200scrolls (e.g., translates in an upward direction) boarding pass detailsuser interface 1326, as shown at FIG. 13N. At FIG. 13N, electronicdevice 1200 displays code 1310 at a center position of display 1202. Insome embodiments, swipe gesture 1350 l causes electronic device 1200 todisplay boarding pass details user interface 1326 with code 1310positioned at the center position of display 1202. In some embodiments,electronic device 1200 displays code 1310 in the full screen mode aftercode 1310 has been displayed at the center position of display 1202 fora predetermined period of time (e.g., half a second, one second, twoseconds). In some embodiments, electronic device 1200 displays code 1310in the full screen mode at an increased brightness (e.g., 100%brightness) on display 1202 after code 1310 has been paused at thecenter position of display 1202 for the predetermined period of time. Insome embodiments, in response to detecting a swipe gesture whiledisplaying code 1310 in the full screen mode, electronic device 1200continues scrolling through details user interface 1326.

In some embodiments, swipe gesture 1350 l is an input that causeselectronic device 1200 to scroll boarding pass details user interface1326 beyond code 1310 (e.g., without pausing on code 1310). As shown atFIG. 13N, boarding pass details user interface 1326 includes furtherdetails related to the transfer account and/or specific pass associatedwith boarding pass platter 1304 c. For example, boarding pass detailsuser interface 1326 includes boarding time indicator 1326 b (“SFO 8:00AM”) of a flight associated with boarding pass platter 1304 c, landingtime indicator 1326 c (“DEN 11:20 AM) of the flight associated withboarding pass platter 1304 c, flight number indicator 1326 d (“APL2020”)of the flight associated with boarding pass platter 1304 c, gate numberindicator 1326 e (“B-19”) of the flight associated with boarding passplatter 1304 c, boarding group indicator 1326 f (“A”) of the flightassociated with boarding pass platter 1304 c, seat number indicator 1326g (“19C”) of the flight associated with boarding pass platter 1304 c,passenger information indicator 1326 h (e.g., a name “John Appleseed) ofthe flight associated with boarding pass platter 1304 c, additionalinformation user interface object 1326 i, and remove pass user interfaceobject 1326 j.

Turning now to FIG. 13O, electronic device 1200 displays details userinterface 1330 associated with transfer card platter 1304 a in responseto detecting tap gesture 1350 f and/or tap gesture 1350 j. At FIG. 13O,details user interface 1330 includes transfer card platter 1304 a,payment options user interface object 1330 a (e.g., for selectingbetween two account options of the respective transfer account, such as“Debit” or “Credit”), latest transactions area 1332, history area 1334,additional information user interface object 1330 b, and remove carduser interface object 1330 c.

At FIG. 13O, electronic device 1200 detects tap gesture 1350 m onadditional information user interface object 1330 b of details userinterface 1330. In response to detecting tap gesture 1350 m, electronicdevice 1200 displays additional details user interface 1336, as shown atFIG. 13P. At FIG. 13P, additional details user interface 1336 includesinformation related to the transfer account associated with transfercard platter 1304 a. For instance, additional details user interface1336 includes visual indicators of credentials (e.g., balanceinformation, card number, device number, network, pin number, history,user address, privacy policy information, and/or terms and conditionsinformation) corresponding to the transfer account associated withtransfer card platter 1304 a. In some embodiments, additional detailsuser interface 1336 includes multiple visual indicators, where all ofthe multiple visual indicators do not fit on display 1202 at one time(e.g., the multiple visual indicators do not fit on display 1202concurrently with one another). Accordingly, electronic device 1200scrolls additional details user interface 1336 in response to swipegestures on additional details user interface 1336 to display visualindicators that are not initially displayed on display 1202.

At FIG. 13O, latest transactions area 1332 includes first transactionuser interface object 1332 a, second transaction user interface object1332 b, and third transaction user interface object 1332 c. In someembodiments, latest transactions area 1332 of details user interface1330 can include more than three transaction user interface objects orfewer than three transaction user interface objects. At FIG. 13O,electronic device 1200 detects tap gesture 1350 n on third transactionuser interface object 1332 c. In response to detecting tap gesture 1350n on third transaction user interface object 1332 c, electronic device1200 displays transaction details user interface 1338, as shown at FIG.13Q. At FIG. 13Q, transaction details user interface 1338 includesvisual indicators corresponding to further details related to aparticular transaction associated with third transaction user interfaceobject 1332 c performed with the transfer account associated withtransfer card platter 1304 a. In some embodiments, transaction detailsuser interface 1338 includes multiple visual indicators, where all ofthe multiple visual indicators do not fit on display 1202 at one time(e.g., the multiple visual indicators do not fit on display 1202concurrently with one another). Accordingly, electronic device 1200scrolls transaction details user interface 1338 in response to swipegestures on transaction details user interface 1338 to display visualindicators that are not initially displayed on display 1202.

Turning now to FIG. 13R, electronic device 1200 displays transit detailsuser interface 1340 in response to a tap gesture on transit platter 1304f. At FIG. 13R, transit details user interface 1340 includes balanceindicator 1340 a (e.g., “Balance 1—$20.00” and “Balance 2—$100.00”),latest transactions area 1342, history area 1344, additional informationuser interface object 1340 b, service mode user interface object 1340 c,and remove card user interface object 1340 d. In some embodiments, thetransfer account associated with transit platter 1304 f includessub-accounts for different services. For example, the transfer accountincludes a first sub-account for conducting transfers for a bus serviceand a second sub-account for conducting transfers for a subway service.Accordingly, transit platter 1304 f can be utilized to conduct transfersfor different services and/or service operators, such that the transferaccount associated with transit platter 1304 f corresponds tocredentials for the different sub-accounts. In some embodiments,electronic device 1200 detects a particular sub-account that is to beused upon communication with a receiver, and electronic device 1200releases the credentials associated with that particular sub-account.Thus, balance indicator 1340 a includes balance information related toeach sub-account of the transfer account associated with transit platter1304 f.

Turning now to FIG. 13S, electronic device 1200 displays cash detailsuser interface 1346 in response to a tap gesture on cash platter 1304 band/or second cash platter 1304 e. At FIG. 13S, cash details userinterface 1346 includes cash platter 1304 b, balance indicator 1346 a,pending transfers area 1348, completed transfers area 1352, history area1354, additional details user interface object 1346 b, and remove carduser interface object 1346 c. A transfer account associated with cashplatter 1304 b and/or second cash platter 1304 e enables a user torequest and accept transfers using a predefined balance (e.g., transfercredits preloaded into the transfer account associated with cash platter1304 b and/or second cash platter 1304 e). In some embodiments,electronic device 1200 detects user input to request that a transfer bemade to a transfer account of another user and transmits the request toan external device associated with the other user. In some embodiments,the other user must accept the request in order for a transfer to becompleted. In some embodiments, electronic device 1200 receives arequest from an external device of the other user, such that the user ofelectronic device 1200 can accept or deny the request.

At FIG. 13S, electronic device 1200 detects tap gesture 1350 o onpending transfer user interface object 1348 a. In response to detectingtap gesture 1350 o, electronic device 1200 displays pending transferuser interface 1356, as shown at FIG. 13T. At FIG. 13T, pending transferuser interface 1356 includes details indicator 1356 a (“+$30.00 From Mom1/29/20, 2:42 PM”), accept user interface object 1356 b, reject userinterface object 1356 c, status indicator 1356 d, and transactionindicator 1356 e. Accordingly, electronic device 1200 transmits one ormore signals to an external device indicating whether the user hasaccepted or rejected a pending transfer based on user input received onthe pending transfer user interface 1356.

Turning back to FIG. 13S, electronic device detects tap gesture 1350 pon completed transfer user interface object 1352 a of completedtransfers area 1352. In response to detecting tap gesture 1350 p,electronic device 1200 displays completed transfer user interface 1358,as shown at FIG. 13U. At FIG. 13U, completed transfer user interface1358 includes details related to a completed transfer, such as detailsindicator 1358 a (“$20.00 to Jane Appleseed 1/30/20, 7:15 AM”), statusindicator 1358 b, and transaction indicator 1358 c.

FIGS. 13V-13AA illustrate a process for completing a transfer using botha loyalty transfer account and a transfer card transfer account. At FIG.13V, electronic device 1200 displays account user interface 1302 upondetecting user input 1350 a. Therefore, transfer accounts of transferapplication are authorized and activated. In some embodiments,electronic device 1200 also detects a swipe gesture on account userinterface 1302 to scroll the plurality of platters 1304, such thatloyalty card platter 1304 d is positioned at a center of display 1202.Further still, the swipe gesture causes electronic device 1200 to pausescrolling and display loyalty card transfer account platter 1304 dpositioned at the center of display 1202 for the predetermined period oftime (e.g., a half second, one second, two seconds). Accordingly,boarding pass platter 1304 c and concert ticket platter 1304 g aredeemphasized in appearance (e.g., reduced in size, reduced in opacity,blurred, and/or changed in color) as compared to loyalty card platter1304 d. Additionally, account user interface 1302 includes indicator1360 (“Hold Near Reader 2,600 Points”) that prompts a user of electronicdevice 1200 to position electronic device 1200 proximate to a receiverin order to utilize a transfer account associated with loyalty cardplatter 1304 d. In some embodiments, indicator 1306, indicator 1308,and/or indicator 1360 include balance information and/or further detailsthat aid the user of electronic device 1200 in conducting a transfer. Insome embodiments, indicator 1306, indicator 1308, and/or indicator 1360alternate text that is displayed when a transfer account associated witha platter of the plurality of platters is configured to conducttransfers using two different techniques (e.g., Near Field Communicationand/or machine-readable code-based transfers).

At FIG. 13W, the user positions electronic device 1200 proximate toreader 1362. As such, electronic device 1200 displays transfer userinterface 1364 in response to detecting that electronic device 1200 ispositioned within a threshold proximity to reader 1362 (e.g., withinrange of an RF field of reader 1362) and in response to detecting thatcredentials of the transfer account associated with loyalty card platter1304 d have been successfully released (e.g., transmitted by electronicdevice 1200 and accepted by reader 1362 to complete a transfer).Transfer user interface 1364 includes loyalty card platter 1304 d andindicator 1364 a (“Done”) indicating that the transfer of credentials(e.g., an account number) of the transfer account associated withloyalty card platter 1304 d has been completed.

In some embodiments, in response to detecting that the transfer has beencompleted with the transfer account associated with loyalty card platter1304 d, electronic device 1200 displays authorization user interface1370 at FIG. 13X (e.g., without receiving additional user input). AtFIG. 13X, authorization user interface 1370 includes transfer cardplatter 1304 a and indicator 1370 a (“Double Click to Pay”). In someembodiments, authorization user interface 1370 includes another platterof the plurality of platters 1304 associated with a transfer accountthat is to be used in the transaction.

Authorization user interface 1370 includes indicator 1370 a indicatingthat that the transfer account associated with transfer card platter1304 a is not authorized/activated. As such, electronic device 1200detects user input 1350 q (e.g., a double press gesture and/or a doubletap gesture) on side button 1206 of electronic device 1200. In responseto detecting user input 1350 q, electronic device 1200 authorizes thetransfer account associated with transfer card platter 1304 a anddisplays transfer user interface 1372, as shown at FIG. 13Y.

At FIG. 13Y, transfer user interface 1372 includes transfer card platter1304 a and indicator 1372 a (“Hold Near Reader”). Indicator 1372 aprompts a user to position electronic device 1200 proximate to reader1362 to release credentials of the transfer account associated withtransfer card platter 1304 a. At FIG. 13Z, electronic device 1200detects that electronic device 1200 is positioned within a thresholdproximity of reader 1362 and transmits the credentials of the transferaccount to the reader, then displays successful transfer user interface1374. At FIG. 13Z, successful transfer user interface 1374 includestransfer card platter 1304 a and indicator 1374 a (“Done”). Successfuluser interface 1374 is automatically displayed in response to electronicdevice detecting that credentials of the transfer account associatedwith transfer card platter 1304 a have been released and accepted and/orreceived by reader 1362.

Further, electronic device 1200 displays dual transfer user interface1376 after displaying successful user interface 1374 for a predeterminedperiod of time (e.g., one second, two seconds, three seconds, fourseconds, five seconds), as shown at FIG. 13AA. Dual transfer userinterface 1376 includes transfer card platter 1304 a and indicator 1376a (“Loyalty Rewards Accepted”) to indicate that the transaction wascompleted via both the transfer account associated with loyalty cardplatter 1304 d and the transfer account associated with transfer cardplatter 1304 a. Accordingly, a user of electronic device 1200 canrecognize that the transaction is complete and that credentials fromboth transfer accounts were utilized in the transaction.

FIG. 14 is a flow diagram illustrating a method for displaying transferaccounts in accordance with some embodiments. Method 1400 is performedat a computer system (e.g., 100, 300, 500, 600 a, 600 b, 800, 1000,1050, 1200, 1600) that is in communication with a display generationcomponent (e.g., 602 a, 602 b, 802, 1002, 1052, 1202, 1602) and one ormore input devices (e.g., a touch-sensitive surface, a camera, afingerprint sensor, and/or a biometric sensor). Some operations inmethod 1400 are, optionally, combined, the orders of some operationsare, optionally, changed, and some operations are, optionally, omitted.

As described below, method 1400 provides an intuitive way for displayingtransfer accounts linked (e.g., provisioned) to the computer system. Themethod reduces the cognitive burden on a user when interacting with aparticular transfer account linked to the computer system. Forbattery-operated computing systems, enabling a user to interact with aparticular transfer account more easily conserves power and increasesthe time between battery charges.

In method 1400, the computer system (e.g., 1200, a smart device, such asa smartphone or a smartwatch; a mobile device) is in communication witha display generation component (e.g., 1202) and one or more inputdevices (e.g., touch-sensitive surface). The computer system displays(1402), via the display generation component, an account user interface(e.g., 1208, 1302) that includes a plurality of visual representations(e.g., 1210, 1304) of a plurality of different accounts (e.g., includinga first visual representation of a first account and a second visualrepresentation of a second account).

While displaying the account user interface, the computer systemreceives (1404), via the one or more input devices (e.g., via thetouch-sensitive surface and/or via the rotatable input mechanism), ascroll input (e.g., 1250 a, 1350 c, 1350 d, 1350 e, 1350 i, swipe on thetouch-sensitive surface and/or rotation of the rotatable inputmechanism) corresponding to a request to scroll the account userinterface (e.g., 1208, 1302);

In response to receiving the scroll input, (e.g., concurrently) thecomputer system scrolls (1406), via the display generation component,the account user interface (e.g., 1208, 1302) to cause a first visualrepresentation of a first account (e.g., 1210 a, 1304 a) and a secondvisual representation of a second account (e.g., 1210 b, 1304 b) toscroll (e.g., first visual representation to scroll to a first location,second visual representation to scroll to a second location, differentfrom the first location).

Subsequent to receiving the scroll input, while the computer systemdisplays the account user interface (e.g., once the scrolling of theaccount user interface has stopped) (1408), and in accordance with adetermination that the first visual representation of the first account(e.g., 1304 a in FIG. 13D) satisfies a set of selection criteria, wherethe set of selection criteria includes a criterion that is met when thefirst visual representation of the first account is displayed in aselection region (e.g., of the display generation component, of the userinterface) for at least a threshold amount of time (e.g., a non-zerothreshold amount of time), the computer system reduces (1410) (e.g., asin FIG. 13D) a visual emphasis (e.g., opacity and/or size) of the secondvisual representation of the second account (e.g., 1304 b) relative to avisual emphasis of the first visual representation of the first account(e.g., reducing the opacity and/or size of the second visualrepresentation (e.g., visually deemphasizing the visual representationto a predetermined opacity and/or size) without reducing the opacityand/or size of the first visual representation (e.g., without visuallydeemphasizing the indication to the predetermined opacity and/or size)).Subsequent to receiving the scroll input, while the computer systemdisplays the account user interface (e.g., once the scrolling of theaccount user interface has stopped) (1408), and in accordance with adetermination that the second visual representation of the secondaccount (e.g., 1210 b, 1304 c) satisfies the set of selection criteria,the computer system reduces (1412) (e.g., as in FIGS. 12C, 13E) a visualemphasis of the first visual representation of the first account (e.g.,1210 a, 1304 b, 1304 d) relative to a visual emphasis of the secondvisual representation of the second account (e.g., reducing the opacityand/or size of the first visual representation (e.g., visuallydeemphasizing the visual representation to the predetermined opacityand/or size) without reducing the opacity and/or size of the secondvisual representation (e.g., without visually deemphasizing the visualrepresentation to the predetermined opacity and/or size)). In someembodiments, the second visual representation of the second account doesnot satisfy the set of selection criteria when the first visualrepresentation of the first account satisfies the set of selectioncriteria. In some embodiments, the first visual representation of thefirst account does not satisfy the set of selection criteria when thesecond visual representation of the second account satisfies the set ofselection criteria.

Reducing the visual emphasis of other visual representations relative toa particular visual representation of an account when the particularvisual representation meets the set of selection criteria provides theuser feedback about the state of the computer system, and in particularthat the account corresponding to the particular visual representationis currently selected by the computer system. Providing improved visualfeedback to the user enhances the operability of the device and makesthe user-device interface more efficient (e.g., by helping the user toprovide proper inputs and reducing user mistakes whenoperating/interacting with the device) which, additionally, reducespower usage and improves battery life of the device by enabling the userto use the device more quickly and efficiently.

In some embodiments, the first visual representation and the secondvisual representation have the same value (e.g., a second value, 100%opacity) (e.g., have the same size, have the same opacity, and/or thesame visual emphasis) for a visual characteristic while scrolling and,optionally, after scrolling but before the set of selection criteria aremet. In some embodiments, visual representations of multiple accounts(e.g., all displayed visual representations of accounts other than thevisual representation of the account that satisfied the set of selectioncriteria) are visually de-emphasized (e.g., by changing the visualcharacteristic of the visual representations of the multiple accounts toa different value, by reducing the opacity and/or size of the displayedvisual representations) as compared to the visual representations of thesingle account that satisfied the set of selection criteria.

In some embodiments, the set of selection criteria is not met for anyaccount while scrolling the account user interface. In some embodiments,the set of selection criteria ceases to be met for any account inresponse to receiving scroll input to scroll the account user interface.

In some embodiments, the computer system reduces a visual emphasis(e.g., opacity and/or size) of the second visual representation (e.g.,1304 b in FIG. 13D) of the second account relative to a visual emphasisof the first visual representation of the first account (e.g., 1304 a inFIG. 13D) by reducing an opacity of the second visual representationrelative to the first visual representation. In some embodiments, thecomputer system reduces a visual emphasis (e.g., opacity and/or size) ofthe first visual representation of the first account (e.g., 1210 a, 1210c in FIG. 12C, 1304 b, 1304 d in FIG. 13E) relative to a visual emphasisof the second visual representation of the second account (e.g., 1210 b,1304 c in FIG. 13E) by reducing an opacity of the first visualrepresentation relative to the second visual representation. In someembodiments, reducing the visual emphasis of a representation relativeto a second representation includes ceasing to display (e.g., reducingopacity to zero) the representation while maintaining display of thesecond representation. In some embodiments, reducing the visual emphasisof a representation relative to a second representation includesdarkening display of the representation relative to the secondrepresentation (e.g., making the representation darker while maintainingthe second representation and/or maintain the representation whilemaking the second representation brighter). In some embodiments,reducing the visual emphasis of a representation relative to a secondrepresentation includes blurring display of the representation relativeto the second representation (e.g., making the representation moreblurry while maintaining the second representation and/or maintain therepresentation while making the second representation less blurry). Insome embodiments, the visual emphasis is changed via one or more (orall) of: changing opacity, size, darkening, and blurring of one visualrepresentation relative to a second representation.

Partially fading representations of other accounts when an account isselected provides the user with visual feedback about which account iscurrently selected. Providing improved visual feedback to the userenhances the operability of the device and makes the user-deviceinterface more efficient (e.g., by helping the user to provide properinputs and reducing user mistakes when operating/interacting with thedevice) which, additionally, reduces power usage and improves batterylife of the device by enabling the user to use the device more quicklyand efficiently.

In some embodiments, the one or more input devices includes a rotatableinput mechanism (e.g., 1204, that is rotatable with respect to a body ofthe computer system, a crown of a smartwatch). In some embodiments, thecomputer system receives the scroll input by detecting a rotation of therotatable input mechanism (e.g., 1204).

Using a rotatable input mechanism to scroll a user interface providesusers with the ability to scroll displayed content without obstructingthe displayed content with an input device (e.g., a finger, such asoften needed for a touch-screen), thereby increasing the precision ofscroll inputs and reducing the number of inputs required to scroll to anintended position. Reducing the number of inputs needed to perform anoperation enhances the operability of the device and makes theuser-device interface more efficient (e.g., by helping the user toprovide proper inputs and reducing user mistakes whenoperating/interacting with the device) which, additionally, reducespower usage and improves battery life of the device by enabling the userto use the device more quickly and efficiently.

In some embodiments, the one or more input devices includes atouch-sensitive surface (e.g., that is optionally integrated with thedisplay generation component to form a touch-sensitive display, 1202).In some embodiments, the computer system receives the scroll input bydetecting a scroll gesture (e.g., a swipe input that includes movementof a contact, 1350 c, 1350 i, 1350 k) at the touch-sensitive surface.

Using a touch-sensitive surface to scroll a user interface (e.g., ascompared to keyboard input) provides users with the ability to scrolldisplayed content at various speeds and get concurrent visual feedbackon the scroll progress, such as on a touch-screen, thereby increasingthe precision of scroll inputs and thereby reducing the number of inputsrequired to scroll to an intended position. Reducing the number ofinputs needed to perform an operation enhances the operability of thedevice and makes the user-device interface more efficient (e.g., byhelping the user to provide proper inputs and reducing user mistakeswhen operating/interacting with the device) which, additionally, reducespower usage and improves battery life of the device by enabling the userto use the device more quickly and efficiently.

In some embodiments, subsequent to the computer system receiving thescroll input and while the computer system displays the account userinterface (e.g., 1302) (e.g., once the scrolling of the account userinterface has stopped), in accordance with the determination that thefirst visual representation of the first account satisfies the set ofselection criteria (and, optionally, and in accordance with adetermination that the first account is available for use), the computersystem displays (e.g., in the account user interface), via the displaygeneration component, a balance of the first account (e.g., an amount ofresources (such as available or used) of the first account) (e.g.,without displaying a balance of the second account).

In some embodiments, in accordance with the determination that thesecond visual representation of the second account satisfies the set ofselection criteria (and, optionally, and in accordance with adetermination that the second account is available for use), displaying(e.g., in the account user interface), via the display generationcomponent, a balance of the second account (e.g., an amount of resources(such as available or used) of the second account) (e.g., withoutdisplaying a balance of the first account).

Displaying a balance of an account once the account is selected providesthe user with visual feedback about that account (before the userattempts to use the account (e.g., in a transaction)) without needing toprovide the same feedback about all other accounts provisioned on thecomputer system. Providing improved visual feedback to the user enhancesthe operability of the device and makes the user-device interface moreefficient (e.g., by helping the user to provide proper inputs andreducing user mistakes when operating/interacting with the device)which, additionally, reduces power usage and improves battery life ofthe device by enabling the user to use the device more quickly andefficiently.

In some embodiments, subsequent to the computer system receiving thescroll input and while the computer system displays the account userinterface (e.g., once the scrolling of the account user interface hasstopped), in accordance with the determination that the first visualrepresentation of the first account satisfies the set of selectioncriteria (and, optionally, in accordance with a determination that thefirst account is a first type of account (e.g., an NFC-capable account)and/or in accordance with a determination that the first account isavailable for use), the computer system displays (e.g., in the accountuser interface), via the display generation component, instructions(e.g., 1324, “double-click side button”) to prepare (e.g., forparticipating in transactions) the first account for use (e.g., toauthorize and/or enable an NFC transaction using the first account)(without enabling the second account for use).

In some embodiments, in accordance with the determination that thesecond visual representation of the second account satisfies the set ofselection criteria (and, optionally, in accordance with a determinationthat the second account is a first type of account (e.g., an NFC-capableaccount) and/or in accordance with a determination that the secondaccount is available for use), displaying (e.g., in the account userinterface), via the display generation component, instructions (such asinstructions to provide biometric authentication or interact with ahardware component of the device such as a button or a rotatable inputdevice (e.g., “double-click side button”)) to prepare the second accountfor use (e.g., to authorize and/or enable an NFC transaction using thesecond account) (without enabling the first account for use).

Displaying instructions for the user to perform to cause the computersystem to prepare the selected account for use provides the user withvisual feedback that the currently selected account is not prepared foruse and about what action the user should take to cause the computersystem to prepare the account for use. Providing improved visualfeedback to the user enhances the operability of the device and makesthe user-device interface more efficient (e.g., by helping the user toprovide proper inputs and reducing user mistakes whenoperating/interacting with the device) which, additionally, reducespower usage and improves battery life of the device by enabling the userto use the device more quickly and efficiently.

In some embodiments, subsequent to the computer system receiving thescroll input and while the computer system displays the account userinterface (e.g., once the scrolling of the account user interface hasstopped): in accordance with the determination that the first visualrepresentation of the first account satisfies the set of selectioncriteria and in accordance with a determination that the first accountis prepared (e.g., for participating in transactions) for use (e.g., viaa double-press of a side button of the computer system), the computersystem displays (e.g., in the account user interface), via the displaygeneration component, instructions (e.g., 1306, “hold near reader”,1212, 1308, “tap to view”) to initiate a process to use the firstaccount (e.g., the process including transmitting credentials of thefirst account to a terminal, such as a wireless communication terminalfor NFC transactions, when the computer system is placed in a wirelessfield of the terminal, displaying a machine-readable code (such as a QRcode), perform a transaction).

In some embodiments, in accordance with the determination that the firstvisual representation of the first account satisfies the set ofselection criteria and in accordance with a determination that the firstaccount is not prepared (e.g., for participating in transactions, usingNFC) for use, forgoing displaying (e.g., in the account user interface),via the display generation component, instructions to initiate theprocess to use the first account (and, optionally, instead displayinginstructions (e.g., “double-click side button”) to prepare the firstaccount for use).

Displaying instructions for the user to perform to initiate the processfor using the account provides the user with visual feedback that thecurrently selected account is prepared for use and about what action theuser should take to cause the computer system to use the account (e.g.,in a transaction). Providing improved visual feedback to the userenhances the operability of the device and makes the user-deviceinterface more efficient (e.g., by helping the user to provide properinputs and reducing user mistakes when operating/interacting with thedevice) which, additionally, reduces power usage and improves batterylife of the device by enabling the user to use the device more quicklyand efficiently.

In some embodiments, the computer system displays the instructions toinitiate a process to use the first account in accordance with adetermination that the first account is a first type of account (e.g.,an account that is NFC-capable and not machine-readable code (e.g.,QR-code) capable) and by displaying instructions (e.g., 1306, textualinstructions) to place the computer system within proximity (e.g.,within a range of an NFC field) of a terminal (e.g., a point-of-saleterminal and/or a wireless communication terminal for NFC transactions).

In some embodiments, the computer system displays the instructions toinitiate a process to use the first account in accordance with adetermination that the first account is a second type of account (e.g.,an account that is machine-readable code-capable and is not NFC-capable)and by displaying instructions (e.g., 1308, textual instructions) toprovide an input (e.g., a tap input (1350 g) at a location correspondingto the first visual representation) at the computer system to causedisplay of a readable portion of (e.g., the entirety of) amachine-readable code (e.g., a two-dimensional code (e.g., QR code)and/or a one-dimensional code (e.g., a barcode)) corresponding to thefirst account (e.g., the machine-readable code can be used to authorizea transaction for the account).

In some embodiments, the computer system displays the instructions toinitiate a process to use the first account in accordance with adetermination that the first account is a third type of account (e.g.,an account that is both QR code-capable and NFC-capable) and bydisplaying instructions (e.g., textual instructions) (e.g. displayedalternating (each in turn, in succession, repeatedly) at the samedisplay location) to: place the computer system within proximity (e.g.,within a range of an NFC field) of the terminal (e.g., a point-of-saleterminal and/or a wireless communication terminal for NFC transactions),and provide an input (e.g., a tap input at a location corresponding tothe first visual representation) at the computer system to cause displayof a readable portion of (e.g., the entirety of) a machine-readable code(e.g., a two-dimensional code (e.g., QR code) and/or a one-dimensionalcode (e.g., a barcode)) corresponding to the first account. In someembodiments, the instructions are displayed concurrently. In someembodiments the instructions are displayed at different times (e.g.,automatically alternating between displaying the instruction to placethe computer system within proximity of the terminal and displaying theinstruction to provide an input at the computer system to cause displayof a readable portion of a machine-readable code corresponding to thefirst account.

Displaying instructions for the user to perform to initiate the processfor using the account provides the user with visual feedback that thecurrently selected account is prepared for use by the computer systemand about what action the user should take to cause the computer systemto use the account (e.g., in a transaction). Providing improved visualfeedback to the user enhances the operability of the device and makesthe user-device interface more efficient (e.g., by helping the user toprovide proper inputs and reducing user mistakes whenoperating/interacting with the device) which, additionally, reducespower usage and improves battery life of the device by enabling the userto use the device more quickly and efficiently.

In some embodiments (e.g., when an account is an NFC-capable account),the (displayed) instructions to initiate the process to use (e.g., viaNFC) the account are instructions (e.g., textual instructions) to placethe computer system within proximity (e.g., within a range of an NFCfield) of a terminal (e.g., a point-of-sale terminal and/or a wirelesscommunication terminal for NFC transactions).

In some embodiments (e.g., when an account is a QR code-capableaccount), the (displayed) instructions to initiate the process to use(e.g., via a machine-readable code (such as a QR code)) the account areinstructions (e.g., textual instructions) to provide an input (e.g., atap input at a location corresponding to the first visualrepresentation) at the computer system to cause display of a readableportion of (e.g., the entirety of) a machine-readable code (e.g., atwo-dimensional code (e.g., QR code) and/or a one-dimensional code(e.g., a barcode)) corresponding to the account (e.g., themachine-readable code can be used to authorize a transaction for theaccount).

In some embodiments (e.g., when an account is both QR code-capable andNFC-capable), the (displayed) instructions to initiate the process touse (e.g., via NFC and/or via a machine-readable code (such as a QRcode)) the first account are alternating instructions (e.g., textualinstructions) (e.g., displayed alternating (each in turn, in succession,repeatedly) at the same display location) to: (a) place the computersystem within proximity (e.g., within a range of an NFC field) of aterminal (e.g., a point-of-sale terminal), and (b) provide an input(e.g., a tap input at a location corresponding to the first visualrepresentation) at the computer system to cause display of a readableportion of (e.g., the entirety of) a machine-readable code (e.g., atwo-dimensional code (e.g., QR code) and/or a one-dimensional code(e.g., a barcode)) corresponding to the first account.

In some embodiments, subsequent to the computer system receiving thescroll input and while the computer system displays the account userinterface (e.g., once the scrolling of the account user interface hasstopped), in accordance with the determination that the first visualrepresentation of the first account (e.g., 1304 e in FIG. 13H) satisfiesthe set of selection criteria and in accordance with a determinationthat the first account is not available for use (e.g., the account isdeactivated and/or inaccessible, the account is unable to be preparedfor use in (or participation in) a transaction), the computer systemdisplays a warning (e.g., 1316, error condition) corresponding to thefirst account being not available for use without displaying a balanceof the first account (e.g., an amount of resources (such as available orused) of the first account) without displaying (e.g., even when thefirst account is not prepared for use) instructions (e.g., “double-clickside button”) to prepare the first account for use (e.g., to authorizeand/or enable use of the first account in an NFC transaction).

Displaying a warning that the selected account is not available for useby the computer system provides the user with visual feedback about thestate of the account (before the user attempts to use the account (e.g.,in a transaction)). Providing improved visual feedback to the userenhances the operability of the device and makes the user-deviceinterface more efficient (e.g., by helping the user to provide properinputs and reducing user mistakes when operating/interacting with thedevice) which, additionally, reduces power usage and improves batterylife of the device by enabling the user to use the device more quicklyand efficiently.

In some embodiments, subsequent to using the first account (e.g., usingNFC to transmit credentials of the first account to a terminal for usein a transaction and/or using a machine-readable code to participate ina transaction), the computer system displays status information (e.g.,1364 a, 1374 a, success, and/or failure) for the use of the firstaccount. In some embodiments, using the first account includestransmitting (e.g., when placed into an NFC field of a terminal) accountcredentials (e.g., an account number) of the first account for use in atransaction. Subsequent to transmitting the account credentials, thecomputer system receives (e.g., from a server and/or from the terminal)information regarding the transaction. The electronic device displaysstatus information, based on (and, optionally, in response to) thereceived information, indicating whether the transaction was successfulor failed.

Displaying status information corresponding to the use of an accountprovides the user with visual feedback about whether the computer systemwas able to successfully use the account (e.g., in a transaction).Providing improved visual feedback to the user enhances the operabilityof the device and makes the user-device interface more efficient (e.g.,by helping the user to provide proper inputs and reducing user mistakeswhen operating/interacting with the device) which, additionally, reducespower usage and improves battery life of the device by enabling the userto use the device more quickly and efficiently.

In some embodiments, the computer system displays the status information(e.g., 1364 a, 1374 a) by displaying information (e.g., transactioninformation) corresponding to the first account. In some embodiments,the information includes one or more of: a balance, an entry transitstation, an exit transit station, a commute plan, and a number oftransit trips remaining.

In some embodiments, the transaction information includes a balance(e.g., number of trips remaining on the first account when the firstaccount is a transit account), resulting from use of the first accountin the transaction. In some embodiments, the transaction informationincludes an indication of entry/exit transit stations used for thetransaction (e.g., when the first account is a transit account). In someembodiments, the transaction information includes commute plan (e.g.,month commuter plan, weekly commuter plan) details (e.g., when the firstaccount is a transit account).

Displaying information corresponding to the use of an account providesthe user with visual feedback about the account provisioned onto thecomputer system. Providing improved visual feedback to the user enhancesthe operability of the device and makes the user-device interface moreefficient (e.g., by helping the user to provide proper inputs andreducing user mistakes when operating/interacting with the device)which, additionally, reduces power usage and improves battery life ofthe device by enabling the user to use the device more quickly andefficiently.

In some embodiments, the computer system displays the status information(e.g., 1364 a, 1374 a) in accordance with a determination that a loyaltyaccount was used (e.g., transmitting credentials of a loyalty account tothe terminal) in conjunction with use (e.g., in the same transaction as)of the first account and by displaying a visual representation of theloyalty account (e.g., 1376 a). In some embodiments, the computer systemdisplays the status information (e.g., 1364 a, 1374 a) in accordancewith a determination that the loyalty account was not used inconjunction with use of the first account and by forgoing display of thevisual representation of the loyalty account (e.g., 1376 a).

Displaying a visual representation of a loyalty account when the loyaltyaccount was used in conjunction with a payment account provides the userwith visual feedback about whether the loyalty account was used by thecomputer system. Providing improved visual feedback to the user enhancesthe operability of the device and makes the user-device interface moreefficient (e.g., by helping the user to provide proper inputs andreducing user mistakes when operating/interacting with the device)which, additionally, reduces power usage and improves battery life ofthe device by enabling the user to use the device more quickly andefficiently.

In some embodiments, a loyalty account is an account of a loyaltyprogram that provides a structured marketing effort that rewardscustomers/members. A loyalty account is optionally specific to oneparticular company, store, or chain of stores. A company (such as aretail store or chain of stores) may use a loyalty account to trackpurchases or other information about a user (e.g., a purchaser). Theloyalty account typically entitles the user to a discount on a currentor future purchase and/or an allotment of points that may be used towardfuture purchases or gifts. In some embodiments, loyalty accounts cannotbe used for making payments.

In some embodiments, subsequent to the computer system receiving thescroll input and while the computer system displays the account userinterface (e.g., once the scrolling of the account user interface hasstopped), in accordance with the determination that the first visualrepresentation of the first account satisfies the set of selectioncriteria and that the account user interface (or, optionally, the firstvisual representation of the first account) was displayed in response toa request to view information about one or more accounts withoutpreparing the one or more accounts from the account user interface foruse (e.g., 1350 h, the first input was of a second input type (e.g., atap input on a touch-sensitive surface at a location corresponding to aUI object to cause the computer system to display an application (withthe account user interface) corresponding to the UI object), differentfrom the first input type), the computer system displays, via thedisplay generation component and overlaid on the second visualrepresentation that has reduced visual emphasis, instructions (e.g.,1324, “double-click side button”) to prepare (e.g., for participating intransactions) the first account for use (e.g., to authorize and/orenable an NFC transaction using the first account) (without enabling thesecond account for use).

Displaying instructions (to be performed by the user to have thecomputer system prepare the selected account) overlaid on a visualrepresentation of a different account further de-emphasizes the otheraccount (that is not selected) provides the user with additional visualfeedback about which account is currently selected by the computersystem and that the currently selected account is not prepared for use.Providing improved visual feedback to the user enhances the operabilityof the device and makes the user-device interface more efficient (e.g.,by helping the user to provide proper inputs and reducing user mistakeswhen operating/interacting with the device) which, additionally, reducespower usage and improves battery life of the device by enabling the userto use the device more quickly and efficiently.

In some embodiments, while displaying the instructions to prepare thefirst account for use, the computer system receives input conforming tothe instructions to prepare the first account for use. In response toreceiving the input conforming to the instructions to prepare the firstaccount for use, the computer system prepares the first account for useand enlarges the (visually emphasized) first visual representation,ceases to display the instructions to prepare the first account for use,and displays (e.g., replaces the previous instructions) withinstructions (e.g., overlaid on the second visual representation) toinitiate the process to use the first account (e.g., instructions toplace the computer system within range of a field of a terminal and/orinstructions to tap on the visual representation to cause display of themachine-readable code).

In some embodiments, subsequent to the computer system receiving thescroll input and while the computer system displays the account userinterface (e.g., once the scrolling of the account user interface hasstopped), in accordance with the determination that the second visualrepresentation of the second account satisfies the set of selectioncriteria and that the account user interface (or, optionally, the firstvisual representation of the first account) was displayed in response toa request to view information about one or more accounts withoutpreparing the one or more accounts from the account user interface foruse (e.g., 1350 h, the first input was of a second input type (e.g., atap input on a touch-sensitive surface at a location corresponding to aUI object to cause the computer system to display an application (withthe account user interface) corresponding to the UI object), differentfrom the first input type), and in accordance with a determination thatthe second account is a first type of account (e.g., an account that isNFC-capable and not machine-readable code (e.g., QR-code) capable and/ora payment account), the computer system displays, via the displaygeneration component (e.g., overlaid on the first visual representationthat has reduced visual emphasis), instructions (e.g., 1324,“double-click side button”) to prepare (e.g., for participating intransactions) the second account for use (e.g., to authorize and/orenable an NFC transaction using the first account). In some embodiments,subsequent to the computer system receiving the scroll input and whilethe computer system displays the account user interface (e.g., once thescrolling of the account user interface has stopped), in accordance withthe determination that the second visual representation of the secondaccount satisfies the set of selection criteria and that the accountuser interface (or, optionally, the first visual representation of thefirst account) was displayed in response to a request to viewinformation about one or more accounts without preparing the one or moreaccounts from the account user interface for use (e.g., 1350 h, thefirst input was of a second input type (e.g., a tap input on atouch-sensitive surface at a location corresponding to a UI object tocause the computer system to display an application (with the accountuser interface) corresponding to the UI object), different from thefirst input type), and in accordance with a determination that thesecond account is a second type of account (e.g., an account that ismachine-readable code-capable and is not NFC-capable and/or a passaccount) different from the first type of account, the computer systemforgoes display of, via the display generation component, instructions(e.g., 1324, “double-click side button”) to prepare (e.g., forparticipating in transactions) the second account for use (e.g., as inFIG. 13L).

In some embodiments, a pass account is a non-payment account. Forexample, a pass account is a park pass that provides access to parkattractions or a transit pass that provides access to transit (e.g., busand/or train) services.

Displaying instructions (to be performed by the user to have thecomputer system prepare the selected account) for particular types ofaccounts and not displaying the instructions for other particular typesof accounts provides the user with visual feedback about the type ofaccount currently selected by the computer system and whether theaccount does (or does not) need to be prepared for use (e.g., is notNFC-capable and therefore doesn't need to be prepared use and/or isNFC-capable and does need to be prepared for use). Providing improvedvisual feedback to the user enhances the operability of the device andmakes the user-device interface more efficient (e.g., by helping theuser to provide proper inputs and reducing user mistakes whenoperating/interacting with the device) which, additionally, reducespower usage and improves battery life of the device by enabling the userto use the device more quickly and efficiently.

In some embodiments, while scrolling the account user interface (e.g.,once the scrolling of the account user interface has started), thecomputer system forgoes displaying, via the display generationcomponent, instructions (e.g., “double-click side button”) to prepare(e.g., for participating in transactions) the first account (or anyaccount) for use (e.g., to authorize and/or enable an NFC transactionusing the first account) (without enabling the second account for use)regardless of the type of request that caused the display of the accountuser interface (or, optionally, the first visual representation of thefirst account).

Forgoing displaying instructions to be performed by the user to have thecomputer system prepare an account while scrolling through visualrepresentations of accounts provides the user with visual feedback thatno account is currently selected by the computer system and that anaccount should be selected to prepare the account for use. Providingimproved visual feedback to the user enhances the operability of thedevice and makes the user-device interface more efficient (e.g., byhelping the user to provide proper inputs and reducing user mistakeswhen operating/interacting with the device) which, additionally, reducespower usage and improves battery life of the device by enabling the userto use the device more quickly and efficiently.

In some embodiments, instructions to prepare an account for use are notdisplayed when the set of selection criteria is not met for any account.In some embodiments, the set of selection criteria is not met for anyaccount while scrolling the account user interface. In some embodiments,the set of selection criteria ceases to be met for any account inresponse to receiving scroll input to scroll the account user interface.

In some embodiments, prior to the computer system displaying the accountuser interface (e.g., 1302), the computer system receives a first input.In response to receiving the first input, the computer system displaysthe account user interface, the first input is a request to prepare oneor more accounts from the account user interface for use (e.g., 1350 a,a double-press of a hardware button of the computer system, an inputthat enables one or more accounts provisioned on the computer system fornear field (e.g., NFC) communication) or a request to view informationabout one or more accounts without preparing the one or more accountsfrom the account user interface for use (e.g., 1350 h, a tap input on atouch-sensitive surface at a location corresponding to a UI object tocause the computer system to display an application (with the accountuser interface) corresponding to the UI object).

Displaying the account user interface when either of two differentrequests are received enables the computer system to alternativelydisplay the account user interface in different modes of operation.Displaying the account user interface in response to the requests alsoprovides the user with visual feedback about the state of the computersystem (e.g., account prepared or not prepared for use). Providingimproved visual feedback to the user enhances the operability of thedevice and makes the user-device interface more efficient (e.g., byhelping the user to provide proper inputs and reducing user mistakeswhen operating/interacting with the device) which, additionally, reducespower usage and improves battery life of the device by enabling the userto use the device more quickly and efficiently.

In some embodiments, the computer system receives a second user input(e.g., a tap gesture). In response to receiving the second user inputand in accordance with a determination that the second user inputcorresponds to selection of the first visual representation of the firstaccount (e.g., 1350 g, 1350 j, 1350 k, a tap gesture at a locationcorresponding to the first visual representation), the computer systemdisplays, via the display generation component, details of the firstaccount (e.g., 1326, an expiration date of the first account, and/or oneor more prior transactions of the first account).

In some embodiments, the second user input is received while displayingfirst visual representation of the first account and the second visualrepresentation of the second account, wherein the visual emphasis (e.g.,opacity and/or size) of the second visual representation of the secondaccount is reduced relative to the visual emphasis of the first visualrepresentation of the first account.

Displaying details of a selected account when the visual representationof the selected account is activated (e.g., via a tap gesture) providesthe user with additional details about the selected account that areavailable to the computer system. Providing improved visual feedback tothe user enhances the operability of the device and makes theuser-device interface more efficient (e.g., by helping the user toprovide proper inputs and reducing user mistakes whenoperating/interacting with the device) which, additionally, reducespower usage and improves battery life of the device by enabling the userto use the device more quickly and efficiently.

In some embodiments, (e.g., in accordance with a determination that thefirst account is a second type of account (e.g., an account that ismachine-readable code-capable)), displaying details of the first accountincludes: in accordance with a determination that the first visualrepresentation of the first account was displayed in response to arequest to prepare one or more accounts from the account user interfacefor use (e.g., the first input was of a first input type (e.g., adouble-press of a hardware button of the computer system and/or an inputthat enables one or more accounts provisioned on the computer system fornear field (e.g., NFC) communication)), displaying, via the displaygeneration component, a readable portion of (e.g., the entirety of) amachine-readable code (e.g., a two-dimensional code (e.g., QR code)and/or a one-dimensional code (e.g., a barcode)) corresponding to thefirst account (e.g., the machine-readable code can be used to authorizea transaction for the account); and in accordance with a determinationthat the first visual representation of the first account was displayedin response to a request to view information about one or more accountswithout preparing the one or more accounts from the account userinterface for use, displaying, via the display generation component,information (e.g., displaying the first visual representation,displaying an account name, and/or displaying an image) corresponding tothe first account without displaying the readable portion of (e.g., theentirety of) the machine-readable code corresponding to the firstaccount.

In some embodiments, the details (e.g., 1326) of the first accountincludes additional information pertaining to a previously displayederror indication (e.g., a previously displayed warning corresponding tothe first account being not available for use). In some embodiments, theadditional information provides one or more reasons for why the accountis not available for use (e.g., the account is expired and/or theaccount balance is at (or below a threshold) value (e.g., 0)). In someembodiments, the additional information is displayed below visualrepresentation of the respective account.

Displaying information about a previously displayed warning when thevisual representation of the selected account is activated (e.g., via atap gesture) provides the user with additional details about the stateof the computer system and, in particular, about the warning. Providingimproved visual feedback to the user enhances the operability of thedevice and makes the user-device interface more efficient (e.g., byhelping the user to provide proper inputs and reducing user mistakeswhen operating/interacting with the device) which, additionally, reducespower usage and improves battery life of the device by enabling the userto use the device more quickly and efficiently.

Note that details of the processes described above with respect tomethod 1400 (e.g., FIG. 14) are also applicable in an analogous mannerto the methods described above. For example, methods 700, 900, and 1100optionally include one or more of the characteristics of the variousmethods described above with reference to method 1400. For brevity,these details are not repeated below.

FIG. 15 is a flow diagram illustrating a method for authorizing transferaccounts in accordance with some embodiments. Method 1500 is performedat a computer system (e.g., 100, 300, 500, 600 a, 600 b, 800, 1000,1050, 1200, 1600) that is in communication with a display generationcomponent (e.g., 602 a, 602 b, 802, 1002, 1052, 1202, 1602) and one ormore input devices (e.g., a touch-sensitive surface, a camera, afingerprint sensor, and/or a biometric sensor). Some operations inmethod 1500 are, optionally, combined, the orders of some operationsare, optionally, changed, and some operations are, optionally, omitted.

As described below, method 1500 provides an intuitive way forauthorizing transfer accounts linked (e.g., provisioned) to the computersystem. The method reduces the cognitive burden on a user when using aparticular transfer account linked to the computer system. Forbattery-operated computing systems, enabling a user to utilize aparticular transfer account more easily conserves power and increasesthe time between battery charges.

In method 1500, computer system (e.g., 1200, a smart device, such as asmartphone or a smartwatch; a mobile device) is in communication with adisplay generation component (e.g., 1202) and one or more input devices(e.g., touch-sensitive surface and/or hardware button). The computersystem receives (1502), via the one or more input devices (e.g., via thetouch-sensitive surface and/or via the hardware button), a first input(e.g., 1350 a, 1350 h).

In response to receiving the first input (e.g., 1350 a, 1350 h) (1504),the computer system displays (1506), via the display generationcomponent, an account user interface (e.g., 1208, 1302) that includes afirst visual representation of a first account (e.g., 1210 b, 1304 c,the account user interface including the first visual representation ofthe first account and, optionally, a second visual indication of asecond account). In some embodiments, in response to receiving the firstinput and in accordance with a determination that the first input is ofthe first input type, the computer system enables one or more accounts(e.g., the second account) of a plurality of accounts for NFCcommunication. In some embodiments, in response to receiving the firstinput and in accordance with a determination that the first input is ofthe second input type, the computer system forgoes enabling the one ormore accounts (e.g., the second account) of the plurality of accountsfor NFC communication.

While the computer system displays the first visual representation ofthe first account (e.g., in the selection region, with indications ofother accounts de-emphasized), the computer system receives (1508), viathe one or more input devices (e.g., via the touch-sensitive surface), asecond input (e.g., 1350 g, 1350 k, touch gesture at a locationcorresponding to, tap on) corresponding to selection of the first visualrepresentation of the first account.

In response to receiving the second input corresponding to selection ofthe first visual representation of the first account (1510) and inaccordance with a determination that the first visual representation ofthe first account was displayed in response to a request to prepare oneor more accounts from the account user interface for use (e.g., thefirst input was of a first input type (e.g., 1350 a, a double-press of ahardware button of the computer system and/or an input that enables oneor more accounts provisioned on the computer system for near field(e.g., NFC) communication)), the computer system displays (1512), viathe display generation component, a readable portion of (e.g., theentirety of) a machine-readable code (e.g., a two-dimensional code(e.g., QR code) and/or a one-dimensional code (e.g., a barcode))corresponding to the first account (e.g., 1310 at FIG. 13G, themachine-readable code can be used to authorize a transaction for theaccount, the readable portion of the machine-readable code is a completemachine-readable code that can be scanned (e.g., optically scanned) byan external device to identify the first account). In response toreceiving the second input corresponding to selection of the firstvisual representation of the first account (1510) and in accordance witha determination that the first visual representation of the firstaccount was displayed in response to a request to view information aboutone or more accounts without preparing the one or more accounts from theaccount user interface for use (e.g., the first input was of a secondinput type (e.g., 1350 h, a tap input on a touch-sensitive surface at alocation corresponding to a UI object to cause the computer system todisplay an application (with the account user interface) correspondingto the UI object), different from the first input type), the computersystem displays (1514), via the display generation component,information (e.g., displaying the first visual indication, displaying anaccount name, and/or displaying an image) corresponding to the firstaccount without displaying the readable portion of (e.g., the entiretyof) the machine-readable code corresponding to the first account (e.g.,1326 at FIG. 13M). In some embodiments, receiving scroll input whiledisplaying the information causes the information to scroll off of thedisplay and a (e.g., not full screen) machine-readable code (e.g., atwo-dimensional code (e.g., QR code) and/or a one-dimensional code(e.g., a barcode)) corresponding to the first account to scroll onto thedisplay. In some embodiments, pausing on the machine-readable codecauses the machine readable code to be displayed in a full screen mode.

Alternatively displaying a readable portion of a machine-readable codeof an account or information corresponding to the account based on thetype of request that caused display of the account user interfaceprovides the user with the information the user is likely to be tryingto access, thereby reducing the number of inputs the user should provideto access that information. Reducing the number of inputs needed toperform an operation enhances the operability of the device and makesthe user-device interface more efficient (e.g., by helping the user toprovide proper inputs and reducing user mistakes whenoperating/interacting with the device) which, additionally, reducespower usage and improves battery life of the device by enabling the userto use the device more quickly and efficiently.

In some embodiments, the computer system displays, via the displaygeneration component, the readable portion of (e.g., the entirety of) amachine-readable code (e.g., a two-dimensional code (e.g., QR code)and/or a one-dimensional code (e.g., a barcode)) corresponding to thefirst account (e.g., 1310 at FIG. 13G, displayed in accordance with thedetermination that the first visual representation of the first accountwas displayed in response to the request to prepare one or more accountsfrom the account user interface for use) at a first brightness level. Insome embodiments, the information (e.g., displaying the first visualindication, displaying an account name, and/or displaying an image)corresponding to the first account (e.g., 1326 at FIG. 13M, displayed inaccordance with a determination that the first visual representation ofthe first account was displayed in response to a request to viewinformation about one or more accounts without preparing the one or moreaccounts from the account user interface for use) is displayed via thedisplay generation component at a second brightness level that is lessthan the first brightness level.

In some embodiments, in response to receiving the second inputcorresponding to selection of the first visual representation of thefirst account and in accordance with a determination that the firstvisual representation of the first account was displayed in response toa request to prepare one or more accounts from the account userinterface for use, the computer system increases (e.g., to a maximumbrightness and/or to a predefined brightness) the display brightness ofthe display generation component. In some embodiments, in response toreceiving the second input corresponding to selection of the firstvisual representation of the first account and in accordance with adetermination that the first visual representation of the first accountwas displayed in response to a request to view information about one ormore accounts without preparing the one or more accounts from theaccount user interface for use, the computer system forgoes increasing(e.g., to the maximum brightness and/or to the predefined brightness)the display brightness and, optionally, maintains the displaybrightness.

Increasing the brightness of displayed content when the displayedcontent is intended to be optically ready by an external device (e.g., aterminal) enables the computer system to better (e.g., from a furtherdistance and/or in more types of lighting conditions) communicate thedisplayed content to the external device. Increasing the brightnesswithout requiring further user input enhances the operability of thedevice and makes the user-device interface more efficient (e.g., byhelping the computer system to provide displayed content and reducinguser mistakes) which, additionally, reduces power usage and improvesbattery life of the device by enabling the user to use the device morequickly and efficiently.

In some embodiments, while the computer system displays the readableportion of (e.g., the entirety of) the machine-readable code (e.g., atwo-dimensional code (e.g., QR code) and/or a one-dimensional code(e.g., a barcode)) corresponding to the first account (e.g., 1310 atFIG. 13G), the computer system receives, via the one or more inputdevices, a scroll input (e.g., 1350 l, swipe on the touch-sensitivesurface, and/or rotation of the rotatable input mechanism). In responseto receiving the scroll input (e.g., 1350 l), the computer systemdisplays details (e.g., 1326 b-326 j, information corresponding to thefirst account; an expiration date of the first account, one or moreprior transactions of the first account, travel informationcorresponding to the first account, and/or address informationcorresponding to the first account) of the first account (e.g., byscrolling at least a portion of the machine-readable code off of thedisplay generation component and concurrently scrolling the details ontothe display generation component).

Displaying details of an account via a scroll input (received whiledisplayed the readable portion of the machine-readable code) providesthe user with additional details about the account that are available tothe computer system. Providing improved visual feedback to the userenhances the operability of the device and makes the user-deviceinterface more efficient (e.g., by helping the user to provide properinputs and reducing user mistakes when operating/interacting with thedevice) which, additionally, reduces power usage and improves batterylife of the device by enabling the user to use the device more quicklyand efficiently.

In some embodiments, details are displayed via the display generationcomponent at the first brightness level that is more than the secondbrightness level at which the machine-readable code was displayed.

In some embodiments, the displayed information corresponding to thefirst account includes a visual representation of the first account(e.g., 1326 at FIG. 13M), at least some of (e.g., not all of) theportion of the machine-readable code (e.g., 1310 at FIG. 13M), and oneor more details (e.g., 1326 a, an indication that the account has aparticular status, such as TSA pre-check) of the first account, the oneor more details of the first account displayed between the visualrepresentation of the first account and the at least some of the portionof the machine-readable code.

Displaying one or more details of an account positioned between thevisual representation of the account and the machine-readable codecorresponding to the account provides the user with additional detailsabout the account that are available to the computer system, and whichare displayed while scrolling to display the machine-readable code.Providing improved visual feedback to the user enhances the operabilityof the device and makes the user-device interface more efficient (e.g.,by helping the user to provide proper inputs and reducing user mistakeswhen operating/interacting with the device) which, additionally, reducespower usage and improves battery life of the device by enabling the userto use the device more quickly and efficiently.

In some embodiments, visual representations of accounts of a first type(e.g., 1304 a in FIG. 13B, a payment accounts, corresponding to paymentcards) are displayed in the account user interface with a respectiveheight (e.g., a height that is less than a height of the display) andvisual representations of accounts of a second type (e.g., 1304 b inFIG. 13B, non-payment accounts, corresponding to non-payment passes) aredisplayed in the account user interface with the respective height.

In some embodiments, visual representations are displayed in the accountuser interface with a same height (and, optionally, same shape and size)independent of the type of account the visual representation represents(e.g., a visual representation of a payment account is the same height(and, optionally, size) as a visual representation of a pass account).

Displaying visual representations of various types of accounts using thesame height enables the computer system to provide the user withfeedback about what displayed objects are visual representations ofaccounts (e.g., if an object has a specific height, the user can haveconfidence that it corresponds to an account). Providing improved visualfeedback to the user enhances the operability of the device and makesthe user-device interface more efficient (e.g., by helping the user toprovide proper inputs and reducing user mistakes whenoperating/interacting with the device) which, additionally, reducespower usage and improves battery life of the device by enabling the userto use the device more quickly and efficiently.

In some embodiments, the first visual representation of the firstaccount (e.g., 1304 c) includes display of one or more datacorresponding to the first account, the one or more data selected from aplurality of data corresponding to the first account (e.g., selectedbased on one or more rules, such as prioritization rules based on thetype of data available for the first account). In some embodiments, thefirst visual representation of the first account does not include otherdata of the plurality of data corresponding to the first account.

Displaying one or more data corresponding to the first account as partof the visual representations enables the computer system to provide theuser with feedback about the accounts, thereby better allowing the userto select the intended account without needing to select multipleaccounts to find the intended account. Reducing the number of inputsneeded to perform an operation enhances the operability of the deviceand makes the user-device interface more efficient (e.g., by helping theuser to provide proper inputs and reducing user mistakes whenoperating/interacting with the device) which, additionally, reducespower usage and improves battery life of the device by enabling the userto use the device more quickly and efficiently.

In some embodiments, the one or more data includes data (e.g., passengername, travel date, travel company, and/or travel destination) todisambiguate the first visual representation of the first account fromother visual representations of other accounts of the account userinterface. In some embodiments, the data to disambiguate the firstvisual representation is selected based on disambiguating the firstvisual representation from the other visual representations of otheraccounts of the account user interface.

In some embodiments, the one or more data of the first visualrepresentation of the first account includes different information ascompared to one or more data of a second visual representation of asecond account, thereby enabling the two visual representations andtheir corresponding accounts to be separately identified by the user.

Displaying one or more data to disambiguate the first account from otheraccounts enables the computer system to provide the user with feedbackabout the account, thereby better allowing the user to select theintended account without needing to select multiple accounts to find theintended account. Reducing the number of inputs needed to perform anoperation enhances the operability of the device and makes theuser-device interface more efficient (e.g., by helping the user toprovide proper inputs and reducing user mistakes whenoperating/interacting with the device) which, additionally, reducespower usage and improves battery life of the device by enabling the userto use the device more quickly and efficiently.

In some embodiments, the one or more data includes an indication (e.g.,a logo of a merchant, a store name, and/or a name of an application) ofa source of the first account.

Displaying an indication of a source of the first account enables thecomputer system to provide the user with feedback about the account,thereby better allowing the user to select the intended account withoutneeding to select multiple accounts to find the intended account.Reducing the number of inputs needed to perform an operation enhancesthe operability of the device and makes the user-device interface moreefficient (e.g., by helping the user to provide proper inputs andreducing user mistakes when operating/interacting with the device)which, additionally, reduces power usage and improves battery life ofthe device by enabling the user to use the device more quickly andefficiently.

In some embodiments, while the computer system displays the account userinterface that includes the first visual representation of a firstaccount, the computer system receives a second scroll input (e.g., 1350c, swipe on the touch-sensitive surface, and/or rotation of therotatable input mechanism). In response to receiving the second scrollinput, the computer system displays in the account user interface, viathe display generation component, a second visual representation of asecond account (e.g., 1304 d, by scrolling the first visualrepresentation on the display generation component and scrolling thesecond visual representation of the second account onto the displaygeneration component). Subsequent to the computer system receiving thesecond input corresponding to selection of the first visualrepresentation of the first account (e.g., while displaying theinformation (e.g., displaying an account name, displaying an image,and/or displaying a non-readable/incompletion part of themachine-readable code) corresponding to the first account withoutdisplaying the readable portion of (e.g., the entirety of) themachine-readable code corresponding to the first account), the computersystem receives a third scroll input (e.g., 1350 l, swipe on thetouch-sensitive surface, and/or rotation of the rotatable inputmechanism). In response to receiving the third scroll input, thecomputer system displays additional information (e.g., 1326 b-1326 h,account details, such as an expiration date, a name of an accountholder, a travel date, flight information, and/or billing address)corresponding to the first account (e.g., without displaying informationcorresponding to another account).

Displaying additional visual representations of other accounts whenreceiving a scroll input while displaying the account user interface anddisplaying details about the first account while displaying themachine-readable code of the first account enables the computer systemto provide the user with feedback on the other content (accounts vs.details) of the respective user interface being accessed. Providingimproved visual feedback to the user enhances the operability of thedevice and makes the user-device interface more efficient (e.g., byhelping the user to provide proper inputs and reducing user mistakeswhen operating/interacting with the device) which, additionally, reducespower usage and improves battery life of the device by enabling the userto use the device more quickly and efficiently.

In some embodiments, the first account is a loyalty account (ornon-payment account). In some embodiments, in response to using thefirst account (e.g., as shown in FIG. 13V-13W, in a process, such as amerchant or purchase transaction; transmitting, such as by NFC,credentials of the first account to a terminal; and/or providing acomputer-generated code to a terminal) (and, optionally, in accordancewith a determination that the first account is a non-payment account (ora loyalty account)), the computer system displays a second visualindication of a second account (e.g., 1304 a) for use (e.g., in the sameprocess), the second account is a payment account.

In some embodiments, the first account is a loyalty account and thesecond account is a payment account. The computer system detects thatthe loyalty account was used in a transaction and prompts the user touse the payment account as part of the same transaction. In someembodiments, after using a loyalty account the computer system prompts(e.g., via display) for use of a payment account.

Displaying a visual indication of a second account after use of a firstaccount enables the computer system to provide the user with a moredirect access to an account that is likely to be used (e.g., user islikely to use the second account after using the first account).Performing an operation when a set of conditions has been met withoutrequiring further user input enhances the operability of the device andmakes the user-device interface more efficient (e.g., by helping theuser to provide proper inputs and reducing user mistakes whenoperating/interacting with the device) which, additionally, reducespower usage and improves battery life of the device by enabling the userto use the device more quickly and efficiently.

In some embodiments, the computer system displays, via the displaygeneration component, a readable portion of (e.g., the entirety of) themachine-readable code corresponding to the first account by scrolling(e.g., as in FIGS. 13F-13G), via the display generation component,content (e.g., a visual representation of the first account, one or moredetails (e.g., an indication that the account has a particular status,such as TSA pre-check) of the first account, at least some of (e.g., notall of) the portion of the machine-readable code) to display thereadable portion of (e.g., the entirety of) the machine-readable codecorresponding to the first account.

Scrolling through content corresponding to the first account to displaythe machine-readable code corresponding to the first account providesthe user with feedback on how to access the content (e.g., by scrolling)once the machine-readable code is displayed. Providing improved visualfeedback to the user enhances the operability of the device and makesthe user-device interface more efficient (e.g., by helping the user toprovide proper inputs and reducing user mistakes whenoperating/interacting with the device) which, additionally, reducespower usage and improves battery life of the device by enabling the userto use the device more quickly and efficiently.

In some embodiments, while the computer system displays information(e.g., displaying the first visual indication, displaying an accountname, and/or displaying an image) corresponding to the first accountwithout displaying the readable portion of (e.g., the entirety of) themachine-readable code corresponding to the first account (e.g., as shownin FIG. 13M), the computer system receives a fourth scroll input (e.g.,1350 l, swipe on the touch-sensitive surface, and/or rotation of therotatable input mechanism). In response to receiving the fourth scrollinput, the computer system scrolls the additional information.Subsequent to scrolling the additional information and in accordancewith a determination that the readable portion of (e.g., the entiretyof) the machine-readable code corresponding to the first account isdisplayed in a selection region (e.g., of the display generationcomponent and/or of the user interface) for at least a threshold amountof time (e.g., a non-zero threshold amount of time), the computer systemincreases (e.g., to a maximum brightness and/or to a predefinedbrightness) the brightness with which the readable portion of (e.g., theentirety of) the machine-readable code is displayed. In some examples,the brightness of the readable portion of the machine-readable code isincreased by increase the display brightness of the display generationcomponent.

Increasing the brightness of displayed content when the displayedcontent is intended to be optically ready by an external device (e.g., aterminal) enables the computer system to better (e.g., from a furtherdistance and/or in more types of lighting conditions) communicate thedisplayed content to the external device. Increasing the brightnesswithout requiring further user input enhances the operability of thedevice and makes the user-device interface more efficient (e.g., byhelping the computer system to provide displayed content and reducinguser mistakes) which, additionally, reduces power usage and improvesbattery life of the device by enabling the user to use the device morequickly and efficiently.

In some embodiments, subsequent to scrolling the additional information,in accordance with a determination that the readable portion of themachine-readable code corresponding to the first account is notdisplayed in the selection region for at least the threshold amount oftime, the computer system foregoes increase the brightness with whichcontent (if a part of (not all of) the machine-readable code) isdisplayed.

In some embodiments, subsequent to scrolling the additional information,in accordance with a determination that the readable portion of (e.g.,the entirety of) the machine-readable code corresponding to the firstaccount is displayed in a selection region (e.g., of the displaygeneration component and/or of the user interface) for at least athreshold amount of time (e.g., a non-zero threshold amount of time),the computer systems updates display of the machine-readable code to bein a full-screen display.

In some embodiments, subsequent to using the first account and inaccordance with a determination that the first account is a pass of agroup of passes (e.g., amusement park passes for family), automaticallydisplaying a visual representation of a subsequent pass of the group ofpasses and prepare the subsequent pass for use without requiringadditional user input. In some embodiments, subsequent to using thefirst account and in accordance with a determination that the firstaccount is a pass of a group of passes (e.g., amusement park passes forfamily), automate the process for using a subsequent pass of the groupof passes, such as illustrated and described with respect to FIGS. 8A-8Fand 9.

Note that details of the processes described above with respect tomethod 1500 (e.g., FIG. 15) are also applicable in an analogous mannerto the methods described above. For example, methods 700, 900, 1100, and1400 optionally include one or more of the characteristics of thevarious methods described above with reference to method 1500. Forbrevity, these details are not repeated below.

FIG. 16A illustrates an electronic device 1600 with display 1602 (e.g.,touch screen) and one or more input devices (e.g., side button 1604). AtFIG. 16A, electronic device 1600 displays, on display 1602, account userinterface 1606 (e.g., similar to account user interface 1700 describedbelow with reference to FIG. 17A). Electronic device 1600 displays aplurality of user interface objects 1608 associated with respectivecomputer storage accounts of a user on account user interface 1606. Therespective computer storage accounts of the user include a variousamounts of (e.g., cloud-based) computer storage resources. In someembodiments, different types of data (e.g., data corresponding to photofiles, data corresponding to document files, data corresponding to musicfiles, data corresponding to video files, and/or data corresponding toapplication files) can be stored and/or archived in the computer storageresources associated with the computer storage accounts. Accordingly, inresponse to detecting user input corresponding to a selection of a userinterface object of the plurality of user interface objects 1608,electronic device 1600 displays information related to the computerstorage resources (e.g., amount of data available and/or amount of dataconsumed) associated with the respective computer storage accountcorresponding to the selected user interface object.

At FIG. 16A, electronic device 1600 displays storage card user interfaceobject 1608 a, memory user interface object 1608 b, shared data userinterface object 1608 c, distributed storage account user interfaceobject 1608 d, remote storage account user interface object 1608 e, andback up storage account user interface object 1608 f on account userinterface 1606.

A user of electronic device 1600 may wish to search for varioustransfers of files and/or transfers of storage allocation related tocomputer storage resources of the computer storage accounts. As setforth below with reference to FIGS. 16B and 16C, account user interface1606 enables the user to search a specific computer storage accountrepresented by a particular user interface object of the plurality ofuser interface objects 1608 and to search multiple (e.g., all) computerstorage accounts linked to electronic device 1600.

At FIG. 16A, electronic device 1600 detects tap gesture 1650 a on searchuser interface object 1606 a (e.g., universal search user interfaceobject). In response to detecting tap gesture 1650 a, electronic device1600 displays universal search user interface 1610, as shown at FIG. 16B(e.g., universal search user interface 1610 displays search resultsafter electronic device 1600 detects user inputs corresponding to asearch term). Alternatively, at FIG. 16A, electronic device 1600 detectstap gesture 1650 b on storage card user interface object 1608 a. Inresponse to detecting tap gesture 1650 b, electronic device 1600displays a details user interface (e.g., similar to details userinterface 1710, described below with reference to FIG. 17B). At FIG.16B, while displaying the details user interface, electronic device 1600detects a tap gesture on search user interface object of the detailsuser interface. In response to detecting the tap gesture, electronicdevice displays single account search user interface 1612, as shown atFIG. 16C (e.g., single account search user interface 1612 displayssearch results after electronic device 1600 detects user inputscorresponding to a search term).

At FIG. 16B, universal search user interface 1610 includes search baruser interface object 1610 a, search narrowing area 1614, account area1616, deletions area 1618, and transactions area 1620. Universal searchuser interface 1610 includes results that match search term 1610 b(“Document”) input into search bar user interface object 1610 a via userinput. As such, electronic device 1600 compares search term 1610 b todata files, computer storage accounts, transactions (e.g., reallocationof storage), and/or other information related to computer storageaccounts for multiple (e.g., all) computer storage accounts linked toelectronic device. For example, account area 1616 of universal searchuser interface 1610 includes particular computer storage accounts (e.g.,“Cards”) that include information based on (e.g., that matches) searchterm 1610 b. In some embodiments, user input on account user interfaceobject 1616 a and/or account user interface object 1616 b causeselectronic device 1600 to display details associated with a particularcomputer storage account that is relevant to search term 1610 b.

At FIG. 16C, single account search user interface 1612 includes searchbar user interface object 1612 a, search narrowing area 1622, categoriesarea 1624, programs area 1626, and transactions area 1628. As set forthabove, results displayed in single account search user interface 1612are associated with a single computer storage account (e.g., computerstorage account represented by storage card user interface object 1608a). Accordingly, single account search user interface 1612 includes onlydata files, transactions, and/or other information related to a singlecomputer storage account (e.g., computer storage account represented bystorage card user interface object 1608 a). Single account search userinterface 1612 does not include accounts area 1616 because results onlyinclude information from a single computer storage account that issearched by electronic device 1600. Therefore, user interface objectsincluded in search narrowing area 1622, categories area 1624, programsarea 1626, and transactions area 1628 are specific to the singlecomputer storage account (e.g., computer storage account represented bystorage card user interface object 1608 a).

Turning now to FIGS. 17A-17N, FIG. 17A illustrates electronic device1600 displaying account user interface 1700 for a transfer accountapplication of electronic device 1600. At FIG. 17A, account userinterface 1700 includes a plurality of user interface objects 1702associated with respective transfer accounts (e.g., payment accounts,such as a third-party credit card account, a debit card account, and/ora stored-value account; pass accounts; ticket accounts; point accounts;rewards accounts; and/or transit accounts) linked to (e.g., provisionedonto) electronic device 1600. In some embodiments, a user can provisionelectronic device 1600 with one or more transfer accounts and use thetransfer accounts to conduct transfers. For example, upon receivingaccess to the transfer account of a user, electronic device 1600receives and stores credentials associated with the transfer account(e.g., account numbers, pin codes, authorization codes, pass codes, cardnumber, balance information, and/or address) in a secure element ofelectronic device 1600. Electronic device 1600 releases (e.g.,transmits) the credentials associated with the transfer account to aterminal (e.g., a wireless communication terminal and/or an NFCterminal) when the transfer account is activated and/or authorized bythe user (e.g., via user input 1750 i at FIG. 17L, user input 1750 k atFIG. 17M, and/or user input 1750 l at FIG. 17N).

Similar to account user interface 1606, account user interface 1700includes search user interface object 1700 a (e.g., universal searchuser interface object) and plurality of user interface objects 1702corresponding to respective transfer accounts linked to electronicdevice 1600. In some embodiments, account user interface 1700 separatesthe plurality of user interface objects 1702 into a transfer accountarea 1704 and a pass account area 1706. At FIG. 17A, transfer accountarea 1704 includes user interface objects representing transfer accountsused to conduct transactions and pass account area 1706 includes userinterface objects representing transfer accounts used to provide entryto an event (e.g., a ticket), provide entry to a transportation service(e.g., a boarding pass and/or a transit card), and/or transfer andaccumulate rewards and/or points for particular transactions (e.g.,rewards cards and/or loyalty cards). At FIG. 17A, transfer account area1704 includes transfer card user interface object 1702 a, Bank of Alaskauser interface object 1702 b, and Alaska Fly Premium user interfaceobject 1702 c. Additionally, pass account area 1706 includes boardingpass user interface object 1702 d, frequent shopper user interfaceobject 1702 e, and concert ticket user interface object 1702 f.

As set forth above with reference to FIGS. 16A-16C, a user of electronicdevice 1600 may wish to conduct searches related to data or informationof transfer accounts linked to electronic device 1600. In some cases, auser is interested in searching a particular transfer account, whereasin other cases, the user is interested in generally search multiple(e.g., all) transfer accounts linked to electronic device 1600. As such,account user interface 1700 provides options to search both particulartransfer accounts (e.g., single account search of a transfer accountrepresented by a respective user interface object of the plurality ofuser interface objects 1702) and multiple (e.g., all) transfer accountslinked to electronic device 1600 (e.g., a universal search).

At FIG. 17A, electronic device detects tap gesture 1750 a on transfercard user interface object 1702 a to initiate a process for conducting asingle account search. In response to detecting tap gesture 1750 a,electronic device 1600 displays transfer card details user interface1710 at FIG. 17B. Alternatively, at FIG. 17A, electronic device 1600detects tap gesture 1750 b on search user interface object 1700 a toinitiate a process for conducting a universal search. In response todetecting tap gesture 1750 b, electronic device 1600 displays universalsearch user interface 1712 at FIG. 17E.

At FIG. 17B, electronic device 1600 displays transfer card details userinterface 1710. Transfer card details user interface 1710 is specific tothe transfer account represented by transfer card user interface object1702 a. Accordingly, transfer card details user interface 1710 displaysdetails and information related to (e.g., only) the transfer accountrepresented by transfer card user interface object 1702 a. For example,transfer card details user interface 1710 includes transfer card userinterface object 1702 a, balance user interface object 1710 a, weeklyactivity user interface object 1710 b, payment user interface object1710 c, and latest transactions area 1714.

At FIG. 17B, electronic device 1600 detects tap gesture 1750 c on searchuser interface object 1710 d (e.g., single account search user interfaceobject). In response to detecting tap gesture 1750 c, electronic device1600 displays single account search user interface 1716, as shown atFIG. 17C.

At FIG. 17C, single account search user interface 1716 includes searchbar user interface object 1716 a, cancel user interface object 1716 b,search options area 1718, and keyboard user interface object 1716 c. AtFIG. 17C, electronic device 1600 detects tap gesture 1750 d on searchbar user interface object 1716 a. In some embodiments, electronic device1600 displays keyboard user interface object 1716 c in response todetecting tap gesture 1750 d. In some embodiments, electronic device1600 maintains display of keyboard user interface object 1716 c inresponse to detecting tap gesture 1750 d. Additionally, electronicdevice 1600 detects one or more user inputs (e.g., one or more tapgestures) on keyboard user interface object 1716 c. The one or more userinputs on keyboard user interface object 1716 c correspond to a searchterm (e.g., text) that a user wishes to search (e.g., search the singletransfer account represented by transfer card user interface object 1702a). In some embodiments, electronic device 1600 further detects userinput that causes electronic device 1600 to conduct the search of thesearch term (e.g., search the single transfer account represented bytransfer card user interface object 1702 a for the search term). Inresponse to detecting the user input, electronic device 1600 displayssingle account search results user interface 1720 at FIG. 17D. In someembodiments, electronic device 1600 displays single account searchresults user interface 1720 at FIG. 17D when electronic device 1600detects a first input of the one or more user inputs on keyboard userinterface object 1716 c (e.g., electronic device 1600 begins to displayand update search results on single account search results userinterface 1720 as letters and/or numbers are typed into search bar userinterface object 1716 a).

At FIG. 17D, electronic device 1600 displays single account searchresults user interface 1720 for search term 1720 a (“Alaska”). Singleaccount search results user interface 1720 includes narrowing searcharea 1722, categories area 1724, merchants area 1726, and transactionsarea 1728. Electronic device 1600 displays narrowing criteria userinterface objects 1722 a-d as suggestions for search terms to be addedto search bar user interface object 1720 b in addition to search term1720 a and based on search term 1720 a (e.g., narrowing criteria userinterface objects 1722 a-d correspond to additional search terms thatare relevant to search term 1720 a). Accordingly, in response todetecting user input on one of the narrowing criteria user interfaceobjects 1722 a-d, electronic device 1600 adds a term represented by theselected narrowing criteria user interface object to search bar userinterface object 1720 b. As such, a search of the transfer accountrepresented by transfer card user interface object 1702 a is conductedfor data and/or information based on (e.g., that matches) search term1720 a and/or the additional term represented by the selected one ofnarrowing criteria user interface objects 1722 a-d.

Categories area 1724 includes category user interface objects 1724 a-c.In some embodiments, electronic device 1600 displays particular categoryuser interface objects 1724 a-c that are based on search term 1720 a.For example, electronic device 1600 determines that the transfer accountrepresented by transfer card user interface object 1702 a was used topurchase groceries in the state of Alaska and/or at a particular grocerystore that includes a name with the term “Alaska.” Accordingly, thecategory user interface objects 1724 a-c are specific to (e.g., selectedbased on) both search term 1720 a and the transfer account representedby transfer card user interface object 1702 a.

Similarly, merchants area 1726 includes merchant user interface objects1726 a-d. In some embodiments, electronic device 1600 displaysparticular merchant user interface objects 1726 a-d that are based onsearch term 1720 a. For example, electronic device 1600 determines thatthe transfer account represented by transfer card user interface object1702 a was used to make purchases at merchants in the state of Alaskaand/or at a particular merchant that includes a name with the term“Alaska.” Accordingly, the merchant user interface objects 1726 a-d arespecific to both search term 1720 a and the transfer account representedby transfer card user interface object 1702 a.

At FIG. 17D, transactions area 1728 includes first transaction userinterface object 1728 a corresponding to a transaction for purchasingAlaskan Jade and second transaction user interface object 1728 bcorresponding to a transaction for purchasing donuts at Donut Shop inthe state of Alaska. Both first transaction user interface object 1728 aand second transaction user interface object 1728 b correspond topurchases associated with the transfer account represented by transfercard user interface object 1702 a. Electronic device 1600 matches dataand/or information associated with the transfer account represented bytransfer card user interface object 1702 a to search term 1720 a todetermine the particular transactions included in transactions area1728. Therefore, results included in single account search results userinterface 1720 are specific to (e.g., only) the transfer accountrepresented by transfer card user interface object 1702 a. In otherwords, single account search results user interface 1720 includesinformation associated with the transfer account represented by transfercard user interface object 1702 a, but does not include information(e.g., transactions) associated with the transfer accounts representedby the remaining user interface objects of the plurality of userinterface objects 1702.

As set forth above, electronic device 1600 displays universal searchuser interface 1712 in response to detecting user input 1750 b, as shownat FIG. 17E. As set forth above, universal search user interface 1712 isnot specific to one transfer account linked to electronic device 1600.Therefore, universal search user interface 1712 enables a user to searchfor data and/or information associated with multiple (e.g., all)transfer accounts linked to electronic device 1600.

At FIG. 17E, universal search user interface 1712 includes search baruser interface object 1712 a, cancel user interface object 1712 b,search options area 1730, and keyboard user interface object 1712 c. AtFIG. 17E, electronic device 1600 detects tap gesture 1750 e on searchbar user interface object 1712 a. In some embodiments, electronic device1600 displays keyboard user interface object 1712 c in response todetecting tap gesture 1750 e. In some embodiments, electronic device1600 maintains display of keyboard user interface object 1712 c inresponse to detecting tap gesture 1750 e. Additionally, electronicdevice 1600 detects one or more user inputs (e.g., one or more tapgestures) on keyboard user interface object 1712 c. The one or more userinputs on keyboard user interface object 1716 c correspond to a searchterm (e.g., text) that a user wishes to search (e.g., search themultiple (e.g., all) transfer accounts linked to electronic device1600). In some embodiments, electronic device 1600 further detects userinput that causes electronic device 1600 to conduct the search of thesearch term (e.g., search multiple (e.g., all) transfer accounts linkedto electronic device 1600 for the search term). In response to detectingthe user input, electronic device 1600 displays universal search resultsuser interface 1732 at FIG. 17F. In some embodiments, electronic device1600 displays universal search results user interface 1732 at FIG. 17Fwhen electronic device 1600 detects a first input of the one or moreuser inputs on keyboard user interface object 1712 c (e.g., electronicdevice 1600 begins to display and update search results on universalsearch results user interface 1732 as letters and/or numbers are typedinto search bar user interface object 1712 a).

At FIG. 17E, search options area 1730 includes categories area 1733,merchants area 1734, and people area 1736. In some embodiments, userinterface objects included in search options area 1730 are based on asearch history of the user. In some embodiments, user interface objectsincluded in search options area 1730 are based on the one or more userinputs detected on keyboard user interface object 1712 c (e.g., userinterface objects of search options area 1730 are updated as the usertypes). Search options area 1730 enables a user to select user interfaceobjects related to a particular category, merchant, or person in lieu ofentering a search term in search bar user interface object 1712 a (e.g.,via keyboard user interface object 1712 c). For instance, electronicdevice 1600 detects tap gesture 1750 f on groceries category userinterface object 1733 a. In response to detecting tap gesture 1750 f,electronic device 1600 displays groceries category user interface 1738,as shown at FIG. 17G. Alternatively, electronic device 1600 detects tapgesture 1750 g on food market user interface object 1734 a. In responseto detecting tap gesture 1750 g, electronic device 1600 displays foodmarket user interface 1740, as shown at FIG. 17H. As discussed belowwith reference to FIGS. 17G and 17H, selecting different user interfaceobjects related to different categories, merchants, and/or people enableelectronic device 1600 to display (and a user to view) the same dataand/or information (e.g., the same transaction) associated with atransfer account linked to electronic device 1600.

At FIG. 17F, electronic device 1600 displays universal search resultsuser interface 1732 for search term 1732 a (“Alaska”, received via inputby the user). Similar to single account search results user interface1720, universal search results user interface 1732 includes narrowingsearch area 1742 and transactions area 1744. Universal search resultsuser interface 1732 also include transfer accounts area 1746 and passesarea 1748.

Electronic device 1600 displays narrowing criteria user interfaceobjects 1742 a-d as suggestions for search terms to be added to searchbar user interface object 1732 b in addition to search term 1732 a andbased on search term 1732 a (e.g., narrowing criteria user interfaceobjects 1742 a-d correspond to additional search terms that are relevantto search term 1732 a). Accordingly, in response to detecting user inputon one of narrowing criteria user interface objects 1742 a-d, electronicdevice 1600 adds a term represented by the selected narrowing criteriauser interface object to search bar user interface object 1732 b. Assuch, a search of multiple (e.g., all) transfer accounts linked toelectronic device 1600 is conducted for data and/or information (e.g.,transactions) based on (e.g., that matches) search term 1732 a and/orthe additional term represented by the selected one of narrowingcriteria user interface objects 1742 a-d.

Transfer accounts area 1746 includes particular transfer accounts linkedto electronic device 1600 that are relevant to search term 1732 a (e.g.,include a name that includes search term 1732 a and/or include dataand/or information based on (e.g., that matches) search term 1732 a). AtFIG. 17F, electronic device 1600 displays transfer account userinterface objects 1746 a-b. In some embodiments, transfer account userinterface objects 1746 a-b correspond to transfer accounts having a namethat includes search term 1732 a (or is similar to search term 1732 a).In some embodiments, transfer account user interface objects 1746 a-bcorrespond to transfer accounts having data and/or information thatincludes search term 1732 a (or is similar to or relevant to search term1732 a). Accordingly, universal search results user interface 1732includes results corresponding to transfer accounts linked to electronicdevice 1600, such that results of universal search results userinterface 1732 are not limited to one specific transfer account. In someembodiments, selecting 1746 a (e.g., a tap gesture on 1746 a) causesdisplay of the user interface shown in FIG. 17I.

Similarly, passes area 1748 includes particular passes (e.g., boardingpasses, transit passes, and/or tickets) associated with transferaccounts linked to electronic device 1600 that are relevant to searchterm 1732 a (e.g., include data and/or information (e.g., transactions)selected based on (e.g., that matches) search term 1732 a). At FIG. 17F,electronic device 1600 displays pass user interface objects 1748 a-c. Insome embodiments, pass user interface objects 1748 a-c correspond topasses of transfer accounts having a name that includes search term 1732a (or is similar to search term 1732 a). In some embodiments, pass userinterface objects 1748 a-c correspond to passes of transfer accountshaving data and/or information that includes search term 1732 a (or issimilar to or relevant to search term 1732 a). The transfer accountsrepresented by pass user interface objects 1748 a-c can be differentfrom one another, the same as one another, or include any combination oftransfer accounts linked to electronic device 1600. As such, universalsearch results user interface 1732 includes results of relevant passesof any transfer account linked to electronic device 1600 and are notlimited to a specific transfer account.

At FIG. 17F, transactions area 1744 includes first transaction userinterface object 1744 a corresponding to a transaction for purchasingAlaskan Jade (e.g., the same transaction corresponding to firsttransaction user interface object 1728 a at FIG. 17D) and secondtransaction user interface object 1744 b corresponding to a transactionfor purchasing Alaskan Crab (e.g., a transaction from a differenttransfer account than the transfer account associated with transfer carduser interface object 1702 a). First transaction user interface object1744 a corresponds to the same transaction as first transaction userinterface object 1728 a of single account search results user interface1720. Accordingly, when searching the same term in single account searchuser interface 1716 and universal search user interface 1712, resultsfor the same transaction can be displayed by electronic device 1600.Further, second transaction user interface object 1744 b corresponds toa purchase that is not displayed in single account search results userinterface 1720. Thus, second transaction user interface object 1744 bcorresponds to a transfer account that is different from the transferaccount represented by transfer card user interface object 1702 a (e.g.,the transfer account searched to display single account search resultsuser interface 1720). To determine the transactions to display intransactions area 1744, electronic device 1600 optionally searches for(e.g., matches) search term 1720 a for data and/or informationassociated with multiple (e.g., all) transfer accounts linked toelectronic device 1600. Therefore, results included in universal searchresults user interface 1732 are associated with multiple (e.g., all)transfer accounts linked to electronic device 1600 and not to oneparticular transfer account.

As set forth above, electronic device 1600 optionally displays the samedata and/or information associated with one or more transfer accountslinked to electronic device 1600 in response to selection of differentuser interface objects included in search options area 1730 of universalsearch user interface 1712. At FIG. 17G, electronic device 1600 displaysgroceries category user interface 1738 in response to detecting tapgesture 1750 f. At FIG. 17G, groceries category user interface 1738includes search bar user interface object 1738 a, search term 1738 bincluded in search bar user interface object 1738 a (e.g., selection ofgroceries category user interface object 1732 a causes a search for“groceries”), narrowing search area 1752, transactions area 1754, andlocations area 1756.

Similar to narrowing search area 1722 and narrowing search area 1742,narrowing search area 1752 includes narrowing criteria user interfaceobjects 1752 a-d as suggestions for search terms to be added to searchbar user interface object 1738 a in addition to search term 1738 b andbased on search term 1738 b (e.g., narrowing criteria user interfaceobjects 1752 a-d correspond to additional search terms that are relevantto search term 1738 b).

Transactions area 1754 includes transaction user interface objects 1754a-c corresponding to transactions associated with multiple (e.g., all)transfer accounts linked to electronic device 1600 that include dataand/or information relevant to search term 1738 b. For example, each oftransaction user interface objects 1754 a-c correspond to transactionsfor purchases related to groceries and/or purchases at grocery stores.Particularly, transaction user interface object 1754 a corresponds to atransaction that occurred yesterday at 6:00 PM, at Food Market for$10.00 in Cupertino, Calif. As set forth below, food market userinterface 1740 also includes a user interface object corresponding tothis same transaction.

Locations area 1756 includes location user interface objects 1756 a-bcorresponding to different locations that are relevant to search term1738 b. For example, location user interface objects 1756 a-b correspondto locations where a user of electronic device 1600 conducted thetransactions corresponding to transaction user interface objects 1754a-c. In some embodiments, location user interface objects 1756 a-bcorrespond to locations in addition to those associated with transactionuser interface objects 1754 a-c. Electronic device 1600 matches dataand/or information associated with multiple (e.g., all) transferaccounts linked to electronic device 1600 to determine locations thatare relevant to search term 1738 b (e.g., locations of transactions forgroceries, locations of transactions at grocery stores, and/or locationshaving a name that includes search term 1738 b).

At FIG. 17H, electronic device 1600 displays food market user interface1740 in response to detecting user input 1750 g of FIG. 17E. At FIG.17H, food market user interface 1740 includes search bar user interfaceobject 1740 a, search term 1740 b included in search bar user interfaceobject 1740 a (e.g., selection of food market merchant user interfaceobject 1734 a causes a search for “food market”), narrowing search area1758, transactions area 1760, locations area 1762, and people area 1764.

Similar to narrowing search area 1722, narrowing search area 1742, andnarrowing search area 1752, narrowing search area 1758 includesnarrowing criteria user interface objects 1758 a-d as suggestions forsearch terms to be added to search bar user interface object 1740 a inaddition to search term 1740 b and based on search term 1740 b (e.g.,narrowing criteria user interface objects 1758 a-d correspond toadditional search terms that are relevant to search term 1740 b).

Transactions area 1760 includes transaction user interface objects 1760a-b corresponding to transactions associated with multiple (e.g., all)transfer accounts linked to electronic device 1600 that include dataand/or information relevant to search term 1740 b. For example, each oftransaction user interface objects 1760 a-b correspond to transactionsfor purchases related to the merchant Food Market. Particularly,transaction user interface object 1760 a corresponds to the sametransaction as the transaction corresponding to transaction userinterface object 1754 a of groceries category user interface 1738.Specifically, the transaction corresponding to transaction userinterface object 1760 a occurred yesterday at 6:00 PM, at Food Market,for $10.00, in Cupertino, Calif. Therefore, electronic device 1600displays the same transaction in response to detecting user input ondifferent user interface objects included in search options area 1730 ofuniversal search user interface 1712 when the different user interfaceobjects in search options area 1730 include overlapping data and/orinformation.

Locations area 1762 includes location user interface object 1762 acorresponding to a location of the merchant Food Market. In someembodiments, a merchant includes multiple locations. Accordingly,locations area 1762 of food market user interface 1740 optionallyincludes additional location user interface objects corresponding toother locations of the merchant Food Market where any transfer accountlinked to electronic device 1600 was used to conduct a transactionand/or transfer.

Further, people area 1764 includes person user interface object 1764 a.In some embodiments, recipients of a transfer (e.g., sending money tosomeone) are displayed in people area 1764 of the search results (e.g.,based on a note entered by a user matching the search term). In someembodiments, transfer accounts are accessed and/or utilized by multipleusers (e.g., joint accounts). Accordingly, people area 1764 displaysperson user interface object 1764 a corresponding to a user thatconducted transactions at the merchant Food Market (“John Appleseed”).In some embodiments, people area 1764 includes additional person userinterface objects when another authorized user of a transfer accountlinked to electronic device 1600 conducts a transaction and/or transferat the merchant Food Market.

A user may wish to conduct multiple searches for two different singletransfer accounts instead of conducting a universal search for multiple(e.g., all) transfer accounts linked to electronic device 1600. As such,electronic device 1600 displays search results for each transfer accountlinked to electronic device 1600 in a similar (or the same) formatand/or layout to facilitate user interaction with the transferapplication and to enable a user to find the desired information quicklyand efficiently. For example, FIGS. 17I-17K illustrate another exampleof electronic device 1600 conducting a search for a single transferaccount. FIGS. 17I-17K show that different search results are generatedfor search term “Alaska” for a transfer account represented by AlaskaFly Premium user interface object 1702 c when compared to search resultsfor the transfer account represented by transfer card user interfaceobject 1702 a. However, single account search user interface 1770 atFIG. 17J and single account search user interface 1716 at FIG. 17C, aswell as single account search results user interface 1772 at FIG. 17Kand single account search results user interface 1720 at FIG. 17D,include the same general layout.

In some embodiments, a user may wish to conduct a transfer (e.g., asecure transfer, a secure transaction, and/or an encrypted transaction)using a transfer account of the transfer application using electronicdevice 1600. FIGS. 17L-17N illustrate examples of using electronicdevice 1600 to conduct transfers using transfer accounts associated withtransfer card user interface object 1702 a, Alaska Fly Premium userinterface object 1702 c, and concert ticket user interface object 1702f, respectively.

At 1776 of FIG. 17L, electronic device 1600 displays account userinterface 1700 and detects tap gesture 1750 h on transfer card userinterface object 1702 a. In response to detecting tap gesture 1750 h ontransfer card user interface object 1702 a, electronic device 1600displays details user interface 1710, as shown at 1778 of FIG. 17L. At1778 of FIG. 17L, electronic device 1600 detects user input 1750 i onside button 1604 (e.g., double tap gesture and/or double press gesture).In response to detecting user input 1750 i, electronic device 1600performs biometric authentication (e.g., facial recognition and/orfingerprint matching) of the user and, if successful, displays transferuser interface 1780 at 1782 of FIG. 17L. Transfer user interface 1780includes transfer card user interface object 1702 a, indicator 1780 a,and stack 1780 b of plurality of user interface objects 1702 (e.g., userinterface objects of plurality of user interface objects 1702 withouttransfer card user interface object 1702 a). Indicator 1780 a prompts auser of electronic device 1600 to position electronic device 1600 withina threshold proximity of a receiver (e.g., a wireless communicationterminal, an NFC terminal, and/or a device that is capable of receivingcredentials from electronic device 1600). As such, the user inputauthenticates and/or activates the transfer account associated withtransfer card user interface object 1702 a and enables electronic device1600 to release (e.g., transmit) credentials of the transfer account toconduct a transfer. In some embodiments, electronic device 1600 detectsadditional user input (e.g., face identification, fingerprintidentification, and/or a passcode) after detecting user input 1750 i andprior to displaying transfer user interface 1780. In some embodiments,this transaction is shown in search results when searching using arelated search term.

At 1784 of FIG. 17M, electronic device 1600 displays account userinterface 1700 and detects tap gesture 1750 j on Alaska Fly Premium userinterface object 1702 c. In response to detecting tap gesture 1750 j onAlaska Fly Premium user interface object 1702 c, electronic device 1600displays details user interface 1786 (e.g., similar to details userinterface 1710), as shown at 1788 of FIG. 17M. At 1788 of FIG. 17M,electronic device 1600 detects user input 1750 k on side button 1604(e.g., double tap gesture and/or double press gesture). In response todetecting user input 1750 k, electronic device 1600 performs biometricauthentication (e.g., facial recognition and/or fingerprint matching) ofthe user and, if successful, displays transfer user interface 1790 at1792 of FIG. 17M. Transfer user interface 1790 includes Alaska FlyPremium user interface object 1702 c, indicator 1790 a, and stack 1790 bof plurality of user interface objects 1702 (e.g., user interfaceobjects of plurality of user interface objects 1702 without Alaska FlyPremium user interface object 1702 c). Indicator 1790 a prompts a userof electronic device 1600 to position electronic device 1600 within athreshold proximity of a receiver (e.g., a wireless communicationterminal, an NFC terminal, and/or a device that is capable of receivingcredentials from electronic device 1600). As such, the user inputauthenticates and/or activates the transfer account associated withAlaska Fly Premium user interface object 1702 c and enables electronicdevice 1600 to release (e.g., transmit) credentials of the transferaccount to conduct a transfer. In some embodiments, electronic device1600 detects additional user input (e.g., face identification,fingerprint identification, and/or a passcode) after detecting userinput 1750 k and prior to displaying transfer user interface 1790. Insome embodiments, this transaction is shown in search results whensearching using a related search term.

At 1794 of FIG. 17N, electronic device 1600 displays account userinterface 1700 and detects tap gesture 1750 l on concert ticket userinterface object 1702 f. In response to detecting tap gesture 1750 l onconcert ticket user interface object 1702 f, electronic device 1600displays transfer user interface 1796, as shown at 1798 of FIG. 17N.Transfer user interface 1796 includes concert ticket user interfaceobject 1702 f, indicator 1796 a, and stack 1796 b of plurality of userinterface objects 1702 (e.g., user interface objects of plurality ofuser interface objects 1702 without concert ticket user interface object1702 f). Indicator 1796 a prompts a user of electronic device 1600 toposition electronic device 1600 within a threshold proximity of areceiver (e.g., a wireless communication terminal, an NFC terminal,and/or a device that is capable of receiving credentials from electronicdevice 1600). As such, tap gesture 1750 l enables electronic device 1600to release (e.g., transmit) credentials of the transfer account toconduct a transfer. The transfer account represented by concert ticketuser interface object 1702 f is associated with a pass (e.g., a ticket)and (optionally) does not involve a transfer of credits (e.g., concertticket is already purchased and is being used only to gain entry to avenue of an event instead of transferring funds from transfer account).Accordingly, electronic device 1600 does not detect user input on sidebutton 1604 in order to authenticate and/or activate the transferaccount associated with concert ticket user interface object 1702 f. Insome embodiments, electronic device 1600 detects additional user input(e.g., face identification, fingerprint identification, and/or apasscode) after detecting tap gesture 1750 l and prior to displayingtransfer user interface 1796. In some embodiments, this transaction isshown in the search results when searching using a related search term.

FIG. 18 is a flow diagram illustrating a method for searching one ormore transfer accounts in accordance with some embodiments. Method 1800is performed at a computer system (e.g., 100, 300, 500, 600 a, 600 b,800, 1000, 1050, 1200, 1600) that is in communication with a displaygeneration component (e.g., 602 a, 602 b, 802, 1002, 1052, 1202, 1602)and one or more input devices (e.g., a touch-sensitive surface, acamera, a fingerprint sensor, and/or a biometric sensor). Someoperations in method 1800 are, optionally, combined, the orders of someoperations are, optionally, changed, and some operations are,optionally, omitted.

As described below, method 1800 provides an intuitive way for search oneor more transfer accounts linked (e.g., provisioned) to the computersystem. The method reduces the cognitive burden on a user when searchingfor particular information corresponding to a transfer account linked tothe computer system. For battery-operated computing systems, enabling auser to find the desired information more easily conserves power andincreases the time between battery charges.

In method 1800, the computer system (e.g., 1600, a smart device, such asa smartphone or a smartwatch; a mobile device) is in communication witha display generation component (e.g., 1602) and one or more inputdevices (e.g., touch-sensitive surface). The computer system displays(1802), via the display generation component, a search user interface(e.g., 1610, 1612, 1712, 1716, 1720, 1732, 1738).

While displaying the search user interface, the computer system receives(1804), via the one or more input devices (e.g., via the touch-sensitivesurface and/or via the hardware button), input that includes a searchterm (e.g., 1610 b, 1612 b, 1738 b, 1720 a, 1732 a, a plurality ofalphanumeric characters).

In response to receiving the input that includes the search term (1806)and in accordance with a determination that the search user interfacecorresponds to a plurality of transfer accounts (e.g., a first accountand a second account) provisioned on the computer system and configuredto transfer a resource of the respective transfer account upon userauthorization (e.g., as shown in FIGS. 16B, 17F), the computer systemconcurrently displays (1808), via the display generation component, aplurality of search results (e.g., 1746, 1748, 1744) selected using thesearch term. The plurality of search results include a first searchresult (1810) (e.g., 1744 a) corresponding to a resource transferactivity of (e.g., a transaction using) a first account of the pluralityof transfer accounts and a second search result (1812) (e.g., 1744 b)corresponding to a resource transfer activity of (e.g., a transactionusing) a second account, different from the first account, of theplurality of transfer accounts.

Providing search results corresponding to resource transfer activitiesof a plurality of accounts based on a search term provides the user withfeedback about the resource transfer activities that relate to thesearch term for the plurality of accounts, thereby reducing the need toprovide multiple inputs to conduct multiple searches. Reducing thenumber of inputs needed to perform an operation enhances the operabilityof the device and makes the user-device interface more efficient (e.g.,by helping the user to provide proper inputs and reducing user mistakeswhen operating/interacting with the device) which, additionally, reducespower usage and improves battery life of the device by enabling the userto use the device more quickly and efficiently.

In some embodiments, transfers (e.g., transactions) are secure transfers(e.g., secure transactions, and/or encrypted transactions). In someembodiments, to secure the transfer, a device account number (thatoptionally can only be decrypted with user authorization) is stored in asecure element of the computer system. The device account number isisolated from the operating system of the computer system and is notbacked up during backup processes. After the computer system receivesauthorization (e.g., via authentication and/or via biometricauthentication (face recognition, fingerprint recognition) to performthe transfer (e.g., use the account in the transaction), the secureelement provides (e.g., transmits, wirelessly) device account number anda transaction-specific dynamic security code to the terminal (e.g., awireless communication terminal) along with additional informationneeded to complete the transfer. In some embodiments, the computersystem does not send the actual payment card number. Accordingly, thetransfer is a secure transfer.

Configuring transfer accounts provisioned on the computer system tosecurely transfer a resource provides additional security by helping toprevent the resource from being used without the user's authorization.

In some embodiments (e.g., prior to receiving the input that includesthe search term), the search user interface includes a plurality ofvisual representations (e.g., 1746 a, 1746 b) of a plurality ofdifferent transfer accounts (e.g., the first account and the secondaccount).

Displaying the plurality of visual representations of the plurality ofdifferent transfer accounts provides the user with feedback about whichtransfer accounts are provisioned on the computer system. Providingimproved visual feedback to the user enhances the operability of thedevice and makes the user-device interface more efficient (e.g., byhelping the user to provide proper inputs and reducing user mistakeswhen operating/interacting with the device) which, additionally, reducespower usage and improves battery life of the device by enabling the userto use the device more quickly and efficiently.

In some embodiments, prior to displaying the search user interface, thecomputer system displays, via the display generation component, anaccount user interface that includes a search option. In someembodiments, the account user interface includes a plurality of visualrepresentations of different transfer accounts (e.g., a first visualrepresentation of a first account and a second visual representation ofa second account). In some embodiments, the account user interfaceincludes a single visual representation of a transfer account. Inresponse to detecting activation of the search option and in accordancewith a determination that the account user interface includes (orcorresponds to) a plurality of visual representations of a plurality oftransfer accounts, the computer system displays the search userinterface that corresponds to the plurality of transfer accounts. Inresponse to detecting activation of the search option and in accordancewith a determination that the account user interface includes (orcorresponds to) a single visual representation of a transfer account,the computer system displays the search user interface that correspondsto the single transfer account.

In some embodiments, the transfer accounts correspond to transitaccounts, loyalty accounts, payment accounts, and/or transit accounts.

In some embodiments, while the computer system displays the plurality ofvisual representations (e.g., 1702 a-1702 f, 1746 a, 1746 b) of theplurality of different transfer accounts (e.g., as part of the searchuser interface and/or as part of the account user interface), thecomputer system receives a selection input corresponding to (e.g., 1750a, 1750 h, 1750 j, 1750 l, a tap gesture at a location corresponding to)a visual representation of a respective transfer account. In response toreceiving the selection input corresponding to the visual representationof the respective transfer account, the computer system displays a userinterface (e.g., 1710, 1786, 1796) for use of the respective transferaccount in a transfer (e.g., a transaction).

In some embodiments, the user interface for use of the respectivetransfer account in a transfer includes a search option, which, whenactivated displays the search user interface.

Displaying a user interface for using the respective transfer account ina transfer provides the user with feedback about which transfer accountwill be used if a transfer is performed using the computer system.Providing improved visual feedback to the user enhances the operabilityof the device and makes the user-device interface more efficient (e.g.,by helping the user to provide proper inputs and reducing user mistakeswhen operating/interacting with the device) which, additionally, reducespower usage and improves battery life of the device by enabling the userto use the device more quickly and efficiently.

In some embodiments, while the computer system displays the userinterface (e.g., 1710, 1786, 1796) for use of the respective transferaccount in a transfer (e.g., a transaction), the computer systemreceives authentication input (e.g., 1750 i, 1750 k, double-press of ahardware button and/or biometric input to authorize use of therespective transfer account). In response to receiving theauthentication input and in accordance with the respective transferaccount being the first account (and in accordance with a determinationthat the biometric input corresponds to an authorized input), thecomputer system prepares the first account for use (e.g., for use in atransfer, without preparing the second account for use in the transfer).In response to receiving the authentication input and in accordance withthe respective transfer account being the second account (and inaccordance with a determination that the biometric input corresponds toan authorized input), the computer system prepares the second accountfor use (e.g., for use in a transfer, without preparing the firstaccount for use in the transfer).

Thus, a user authorizes an account to be prepared for use to transfer aresource of the respective account by providing a valid biometric input(e.g., via facial recognition and/or fingerprint recognition).

In some embodiments, using an account in a transaction includestransmitting a signal that includes credentials (e.g., paymentinformation) for the account, such as a payment account. In someembodiments, preparing to use the account in a transaction includesreconfiguring the electronic device (e.g., 100, 300, 500, 600) torespond as a contactless payment card, such as an NFC-enabledcontactless payment card, and then transmitting credentials of theaccount via NFC, such as to a wireless contactless payment terminal. Insome embodiments, subsequent to transmitting credentials of the accountvia NFC, the computer system reconfigures to not respond as acontactless payment card (e.g., requiring authorization before againbeing reconfigured to respond as a contactless payment card via NFC).

In some embodiments, generation of and/or transmission of the signal iscontrolled by a secure element in the electronic device (e.g., 100, 300,500, 600). The secure element optionally requires a particular userinput prior to releasing payment information. For example, the secureelement optionally requires detection that the electronic device isbeing worn, detection of a button press, detection of entry of apasscode, detection of a touch, detection of one or more optionselections (e.g., received while interacting with an application),detection of a fingerprint signature, detection of a voice or voicecommand, detection of a gesture or movement (e.g., rotation and/oracceleration), biometric authentication, and/or facial recognition. Insome examples, if a communication channel (e.g., an NFC communicationchannel) with another device (e.g., a contactless payment terminal) isestablished within a defined time period from detection of the input,the secure element releases payment information to be transmitted to theother device (e.g., the contactless payment terminal). In some examples,the secure element is a hardware component that controls release ofsecure information. In some examples, the secure element is a softwarecomponent that controls release of secure information.

Preparing different accounts for use in a transfer based on a selectionof the account prepares an appropriate transfer account to be used in atransfer. The authentication input helps to prevent unauthorizedtransfers using the prepared account.

In some embodiments, the search user interface (e.g., 1610, 1612, 1712,1716, 1720, 1732, 1738) is generated by a first application and thefirst search result corresponding to the resource transfer activity isbased on data received from a first source different from the firstapplication (e.g., from a third-party application and/or from anexternal source (e.g., from a terminal, such as a wireless communicationterminal for NFC transactions)).

In some embodiments, the second search result corresponding to theresource transfer activity is based on data received from a secondsource different from the first application and the first source.

Displaying search results corresponding to resource transfer activitiesbased on data received from external sources provides the user feedbackabout the data transmitted from the external sources to the computersystem. Providing improved visual feedback to the user enhances theoperability of the device and makes the user-device interface moreefficient (e.g., by helping the user to provide proper inputs andreducing user mistakes when operating/interacting with the device)which, additionally, reduces power usage and improves battery life ofthe device by enabling the user to use the device more quickly andefficiently.

In some embodiments, in response to the computer system receiving theinput that includes the search term and in accordance with adetermination that the search user interface corresponds to the firstaccount (e.g., and not the second account) provisioned on the computersystem and configured to transfer a resource of the first account uponuser authorization (e.g., as in FIGS. 17C, 17D), the computer systemdisplays, via the display generation component, a second plurality ofsearch results (e.g., 1728 a (same as 1744 a), 1728 b). The secondplurality of search results is selected using the search term withoutincluding the second search result (e.g., 1744 b) corresponding to theresource transfer activity of the second account. In some embodiments,the second plurality of search results include the first search result(e.g., 1728 a (same as 1744 a)) corresponding to the resource transferactivity of (e.g., a transaction using) the first account of theplurality of transfer accounts and a third search result (e.g., 1728 b)corresponding to another resource transfer activity of the first accountof the plurality of transfer accounts. In some embodiments, the thirdsearch result is displayed concurrently with the first search result.

Providing search results corresponding to resource transfer activitiesof a single account based on a search term provides the user withfeedback about the resource transfer activities that relate to thesearch term for that specific account, thereby reducing the need for theuser to provide more inputs to find a particular transfer (e.g., whenthe account used for the transfer is already known to the user).Reducing the number of inputs needed to perform an operation enhancesthe operability of the device and makes the user-device interface moreefficient (e.g., by helping the user to provide proper inputs andreducing user mistakes when operating/interacting with the device)which, additionally, reduces power usage and improves battery life ofthe device by enabling the user to use the device more quickly andefficiently.

In some embodiments, when the search user interface corresponds to asingle transfer account, the search results include resultscorresponding to that respective single transfer account and do notinclude results corresponding to other transfer accounts.

In some embodiments, a first set of search results of the plurality ofsearch results are displayed in a first grouping of a plurality ofgroupings of data (e.g., as shown in FIG. 17F) and a second set ofsearch results of the plurality of search results are displayed in asecond grouping of the plurality of groupings of data (e.g., as shown inFIG. 17D).

In some embodiments, the search results are selected by searching aplurality of groupings of data (e.g., same as the multiple groupings).In some embodiments, the plurality of groupings of data includescategories, merchants, people, locations, and accounts. In someembodiments, different search results of the first plurality of searchresults are grouped together and displayed within respective categoriesof the same multiple categories.

Searching a plurality of groupings of data and displaying the resultsgrouped according to the groupings provides more complete searchresults, thereby reducing the need for the user to provide inputs toseparately search each grouping of data. Reducing the number of inputsneeded to perform an operation enhances the operability of the deviceand makes the user-device interface more efficient (e.g., by helping theuser to provide proper inputs and reducing user mistakes whenoperating/interacting with the device) which, additionally, reducespower usage and improves battery life of the device by enabling the userto use the device more quickly and efficiently.

In some embodiments, the plurality of groupings of data includes one ormore of categories (e.g., 1724), merchants (e.g., 1726), people (e.g.,1764), and locations (e.g., 1756). In some embodiments, the plurality ofgroupings of data includes all of: categories, merchants, people, andlocations.

Searching a plurality of groupings of data and displaying the resultsgrouped according to the groupings provides more complete searchresults, thereby reducing the need for the user to provide inputs toseparately search each grouping of data. Reducing the number of inputsneeded to perform an operation enhances the operability of the deviceand makes the user-device interface more efficient (e.g., by helping theuser to provide proper inputs and reducing user mistakes whenoperating/interacting with the device) which, additionally, reducespower usage and improves battery life of the device by enabling the userto use the device more quickly and efficiently.

In some embodiments, the computer system displays the search userinterface prior to receiving the input that includes the search term andby displaying (e.g., as in FIGS. 17C and 17E) respective groupings ofmultiple groupings (e.g., categories, merchants, people, locations,and/or recently searched, same as the plurality of groupings of data).

In some embodiments, each category is visually separated from the othergroupings. In some embodiments, each category includes one or moresearch objects, each search object corresponding to a suggested searchterm relating to the respective category.

Displaying indications of multiple groupings provides the user withfeedback about how the search results will be grouped, thereby enablingthe user to more quickly identify search results of particular interestwhen the search results are displayed. Providing improved visualfeedback to the user enhances the operability of the device and makesthe user-device interface more efficient (e.g., by helping the user toprovide proper inputs and reducing user mistakes whenoperating/interacting with the device) which, additionally, reducespower usage and improves battery life of the device by enabling the userto use the device more quickly and efficiently.

In some embodiments, the computer system concurrently displays theplurality of search results selected using the search term byconcurrently displaying: a first set of one or more search results ofthe plurality of search results in a first grouping; (e.g., 1742, 1746,a first section visually separated from a second section) and a secondset of one or more search results of the plurality of search results ina second grouping (e.g., 1748, 1744, a second section).

Displaying search results grouped into groupings enables the user tomore quickly identify search results of particular interest by firstfinding the grouping of interest. Providing improved visual feedback tothe user enhances the operability of the device and makes theuser-device interface more efficient (e.g., by helping the user toprovide proper inputs and reducing user mistakes whenoperating/interacting with the device) which, additionally, reducespower usage and improves battery life of the device by enabling the userto use the device more quickly and efficiently.

In some embodiments, multiple search results (of the plurality of searchresults) of a first group are displayed in a first group section andmultiple different search results (of the plurality of search results)of a second group are displayed (concurrently with the first group) in asecond group section.

In some embodiments, in response to the computer system receiving theinput that includes the search term and in accordance with adetermination that the search user interface corresponds to the firstaccount, the computer system displays search results (e.g., as in FIG.17D) corresponding to the first account (and not to the second account)by grouping together different results and displaying the groupedresults within respective groupings (e.g., of the multiple groupings).In some embodiments, in response to the computer system receiving theinput that includes the search term and in accordance with adetermination that the search user interface corresponds to the secondaccount, the computer system displays search results (e.g., as in FIG.17K) corresponding to the second account (and not to the first account)by grouping together different results and displaying the groupedresults within the respective groupings (e.g., same groupings as forresults of the first account, of the multiple groupings).

Display similar types of search results in similar groupings across themultiple transfer accounts enables the computer system to provide theuser with consistently formatted results independent of the searchedtransfer account, thereby reducing the number of inputs the user needsto provide to navigate the respective search results. Reducing thenumber of inputs needed to perform an operation enhances the operabilityof the device and makes the user-device interface more efficient (e.g.,by helping the user to provide proper inputs and reducing user mistakeswhen operating/interacting with the device) which, additionally, reducespower usage and improves battery life of the device by enabling the userto use the device more quickly and efficiently.

In some embodiments, while the computer system displays the search userinterface, the computer system receives input (e.g., 1750 f, 1760 g, atap input) selecting an option (e.g., 1733 a, 1734 a) of a grouping(e.g., selecting a search option within a section/grouping). In responseto receiving the input selecting an option of a grouping and inaccordance with a determination that the selected option is a firstoption (e.g., 1733 a, of a first group), the computer system displaysmultiple search results corresponding to the first option. The multiplesearch results corresponding to the first option include a fourth searchresult corresponding to a resource transfer activity (e.g., atransaction using) and a fifth search result corresponding to a resourcetransfer activity and without displaying a sixth search resultcorresponding to a resource transfer activity (e.g., as in FIG. 17G). Insome embodiments, in response to receiving the input selecting an optionof a grouping and in accordance with a determination that the selectedoption is a second option (e.g., 1734 a, of the first grouping, of asecond grouping), the computer system displays multiple search resultscorresponding to the second option. The multiple search resultscorresponding to the second option include the fourth search resultcorresponding to a resource transfer activity (e.g., a transactionusing) and the sixth search result corresponding to a resource transferactivity without displaying the fifth search result corresponding to aresource transfer activity (e.g., as in FIG. 17H).

Displaying the same search result as part of different grouping optionsenables the computer system to provide the user with the relevant searchresult when any group option relevant to the search result is selected,thereby reducing the need for the user to select multiple groupingoptions to find a search result. Providing improved visual feedback tothe user enhances the operability of the device and makes theuser-device interface more efficient (e.g., by helping the user toprovide proper inputs and reducing user mistakes whenoperating/interacting with the device) which, additionally, reducespower usage and improves battery life of the device by enabling the userto use the device more quickly and efficiently.

In some embodiments, selecting options of a category causes display oftransfer activities (e.g., transactions) grouped within a particularoption or grouping. In some embodiments, the same transfer activity canbe grouped under multiple options or groupings, and thus be displayedwhen various options are selected.

In some embodiments, the computer system concurrently displays, via thedisplay generation component, with the plurality of search resultsselected using the search term, a filter option (or a plurality offilter options) (e.g., 1758 a-1758 d) which, when selected, narrows thedisplayed search results. In some embodiments, the plurality of filteroptions include options to narrow the search results by account, bydate, by location (e.g., a particular location), by amount (e.g., lessthan a particular amount), by rewards purchases, by people (e.g., byparticular people involved in the transfer), by transfers performedusing a physical credit card, or by transfer performed using thecomputer system.

Providing filter options to narrow the search results displayed providesthe user with the ability to narrow the search by selecting a singleoption, rather than the used needing to provide multiple inputs to typeout a term by which to narrow the search. Reducing the number of inputsneeded to perform an operation enhances the operability of the deviceand makes the user-device interface more efficient (e.g., by helping theuser to provide proper inputs and reducing user mistakes whenoperating/interacting with the device) which, additionally, reducespower usage and improves battery life of the device by enabling the userto use the device more quickly and efficiently.

In some embodiments, the filter option (or the plurality of filteroptions) is selected based on the received search term (e.g., 1740 b).

Providing filter options based on the received search term provides theuser with the ability to narrow the search by selecting a single option,rather than the used needing to provide multiple inputs to type out aterm by which to narrow the search. Reducing the number of inputs neededto perform an operation enhances the operability of the device and makesthe user-device interface more efficient (e.g., by helping the user toprovide proper inputs and reducing user mistakes whenoperating/interacting with the device) which, additionally, reducespower usage and improves battery life of the device by enabling the userto use the device more quickly and efficiently.

In some embodiments, the filter option (or the plurality of filteroptions) is selected based on prior searches (e.g., prior search termsand/or prior filtering options that were selected by the user).

Providing filter options based on prior searches provides the user withthe ability to narrow the search by selecting a single option, ratherthan the used needing to provide multiple inputs to type out a term bywhich to narrow the search. Reducing the number of inputs needed toperform an operation enhances the operability of the device and makesthe user-device interface more efficient (e.g., by helping the user toprovide proper inputs and reducing user mistakes whenoperating/interacting with the device) which, additionally, reducespower usage and improves battery life of the device by enabling the userto use the device more quickly and efficiently.

In some embodiments, the plurality of search results selected using thesearch term includes one or more (e.g., representations of) paymentaccounts (e.g., 1746 a, 1746 b, the first account, the second account).

Displaying search results that include a payment account enables thecomputer system to provide the user with feedback about payment accountsprovisioned onto the computer system that match the search term.Providing improved visual feedback to the user enhances the operabilityof the device and makes the user-device interface more efficient (e.g.,by helping the user to provide proper inputs and reducing user mistakeswhen operating/interacting with the device) which, additionally, reducespower usage and improves battery life of the device by enabling the userto use the device more quickly and efficiently.

In some embodiments, the computer system receives a selection inputcorresponding to (e.g., a tap gesture at a location corresponding to) apayment account of the one or more payment accounts. In response toreceiving the selection input corresponding to the payment account, thecomputer system displays a user interface for use of the respectivetransfer account in a transfer (e.g., a transaction). Thus, the user cansearch for a payment account and then easily use that payment accountfor a transfer (e.g., an NFC payment).

In some embodiments, the plurality of search results selected using thesearch term includes one or more (e.g., representations of) passaccounts (e.g., 1748 a, 1748 b, 1748 c, the first account, the secondaccount). In some embodiments, a pass account is a non-payment account.In some examples, a pass account is a park pass that provides access topark attractions or a transit pass that provides access to transit(e.g., bus and/or train) services. In some examples, a pass account isan airplane boarding pass that provides access to a secure area of anairport and/or entry to the airplane corresponding to the pass. In someexamples, a pass account is loyalty account. In some embodiments, aloyalty account is an account of a loyalty program that provides astructured marketing effort that rewards customers/members. A loyaltyaccount is optionally specific to one particular company, store, orchain of stores. A company (such as a retail store or chain of stores)may use a loyalty account to track purchases or other information abouta user (e.g., a purchaser). The loyalty account typically entitles theuser to a discount on a current or future purchase and/or an allotmentof points that may be used toward future purchases or gifts. In someembodiments, loyalty accounts cannot be used for making payments. Insome embodiments, the one or more pass accounts are concurrentlydisplayed with one or more payment accounts and/or one or more loyaltyaccounts.

Displaying search results that include a pass account enables thecomputer system to provide the user with feedback about pass accountsprovisioned onto the computer system that match the search term.Providing improved visual feedback to the user enhances the operabilityof the device and makes the user-device interface more efficient (e.g.,by helping the user to provide proper inputs and reducing user mistakeswhen operating/interacting with the device) which, additionally, reducespower usage and improves battery life of the device by enabling the userto use the device more quickly and efficiently.

In some embodiments, the computer system receives a selection inputcorresponding to (e.g., a tap gesture at a location corresponding to) apass account of the one or more pass accounts. In response to receivingthe selection input corresponding to the pass account, the computersystem displays a user interface for use of the respective pass accountin a transfer (e.g., a transaction). Thus, the user can search for apass account and then easily use that pass account for a transfer (e.g.,a transaction, entering a transit station, and/or accessing a ride).

Note that details of the processes described above with respect tomethod 1800 (e.g., FIG. 18) are also applicable in an analogous mannerto the methods described above. For example, methods 700, 900, 1100,1400, and 1500 optionally include one or more of the characteristics ofthe various methods described above with reference to method 1800. Forbrevity, these details are not repeated below.

The foregoing description, for purpose of explanation, has beendescribed with reference to specific embodiments. However, theillustrative discussions above are not intended to be exhaustive or tolimit the invention to the precise forms disclosed. Many modificationsand variations are possible in view of the above teachings. Theembodiments were chosen and described in order to best explain theprinciples of the techniques and their practical applications. Othersskilled in the art are thereby enabled to best utilize the techniquesand various embodiments with various modifications as are suited to theparticular use contemplated.

Although the disclosure and examples have been fully described withreference to the accompanying drawings, it is to be noted that variouschanges and modifications will become apparent to those skilled in theart. Such changes and modifications are to be understood as beingincluded within the scope of the disclosure and examples as defined bythe claims.

As described above, one aspect of the present technology is thegathering and use of data available from various sources share and usepasses or accounts. The present disclosure contemplates that in someinstances, this gathered data may include personal information data thatuniquely identifies or can be used to contact or locate a specificperson. Such personal information data can include demographic data,location-based data, telephone numbers, email addresses, twitter IDs,home addresses, data or records relating to a user's health or level offitness (e.g., vital signs measurements, medication information,exercise information), date of birth, or any other identifying orpersonal information.

The present disclosure recognizes that the use of such personalinformation data, in the present technology, can be used to the benefitof users. For example, the personal information data can be used toprovide access to passes or accounts. Further, other uses for personalinformation data that benefit the user are also contemplated by thepresent disclosure. For instance, health and fitness data may be used toprovide insights into a user's general wellness, or may be used aspositive feedback to individuals using technology to pursue wellnessgoals.

The present disclosure contemplates that the entities responsible forthe collection, analysis, disclosure, transfer, storage, or other use ofsuch personal information data will comply with well-established privacypolicies and/or privacy practices. In particular, such entities shouldimplement and consistently use privacy policies and practices that aregenerally recognized as meeting or exceeding industry or governmentalrequirements for maintaining personal information data private andsecure. Such policies should be easily accessible by users, and shouldbe updated as the collection and/or use of data changes. Personalinformation from users should be collected for legitimate and reasonableuses of the entity and not shared or sold outside of those legitimateuses. Further, such collection/sharing should occur after receiving theinformed consent of the users. Additionally, such entities shouldconsider taking any needed steps for safeguarding and securing access tosuch personal information data and ensuring that others with access tothe personal information data adhere to their privacy policies andprocedures. Further, such entities can subject themselves to evaluationby third parties to certify their adherence to widely accepted privacypolicies and practices. In addition, policies and practices should beadapted for the particular types of personal information data beingcollected and/or accessed and adapted to applicable laws and standards,including jurisdiction-specific considerations. For instance, in the US,collection of or access to certain health data may be governed byfederal and/or state laws, such as the Health Insurance Portability andAccountability Act (HIPAA); whereas health data in other countries maybe subject to other regulations and policies and should be handledaccordingly. Hence different privacy practices should be maintained fordifferent personal data types in each country.

Despite the foregoing, the present disclosure also contemplatesembodiments in which users selectively block the use of, or access to,personal information data. That is, the present disclosure contemplatesthat hardware and/or software elements can be provided to prevent orblock access to such personal information data. For example, the presenttechnology can be configured to allow users to select to “opt in” or“opt out” of participation in the collection of personal informationdata during registration for services or anytime thereafter. In additionto providing “opt in” and “opt out” options, the present disclosurecontemplates providing notifications relating to the access or use ofpersonal information. For instance, a user may be notified upondownloading an app that their personal information data will be accessedand then reminded again just before personal information data isaccessed by the app.

Moreover, it is the intent of the present disclosure that personalinformation data should be managed and handled in a way to minimizerisks of unintentional or unauthorized access or use. Risk can beminimized by limiting the collection of data and deleting data once itis no longer needed. In addition, and when applicable, including incertain health related applications, data de-identification can be usedto protect a user's privacy. De-identification may be facilitated, whenappropriate, by removing specific identifiers (e.g., date of birth,etc.), controlling the amount or specificity of data stored (e.g.,collecting location data a city level rather than at an address level),controlling how data is stored (e.g., aggregating data across users),and/or other methods.

Therefore, although the present disclosure broadly covers use ofpersonal information data to implement one or more various disclosedembodiments, the present disclosure also contemplates that the variousembodiments can also be implemented without the need for accessing suchpersonal information data. That is, the various embodiments of thepresent technology are not rendered inoperable due to the lack of all ora portion of such personal information data. For example, passes oraccounts can be shared and used based on non-personal information dataor a bare minimum amount of personal information, other non-personalinformation, or publicly available information.

What is claimed is:
 1. A computer system, comprising: a displaygeneration component; one or more input devices; one or more processors;and memory storing one or more programs configured to be executed by theone or more processors, the one or more programs including instructionsfor: displaying, via the display generation component, a first userinterface including an indication of an account; receiving, via the oneor more input devices, authentication data; and in response to receivingthe authentication data: in accordance with a determination that theauthentication data satisfies authentication criteria associated withthe account, displaying, via the display generation component, a firstmachine-readable code associated with the account; and in accordancewith a determination that the authentication data does not satisfy theauthentication criteria associated with the account, forgoing display ofthe first machine-readable code associated with the account.
 2. Thecomputer system of claim 1, wherein the one or more programs furtherinclude instructions for: displaying, via the display generationcomponent, a second user interface for an application associated with aservice provider, wherein the account is associated with the serviceprovider; while displaying the second user interface, detecting arequest to configure the account for use in the first user interface;and in response to detecting the request to configure the account foruse in the first user interface, including the indication of the accountin the first user interface.
 3. The computer system of claim 1, whereindisplaying the machine-readable code includes replacing the display ofthe indication of the account with the display of the machine-readablecode.
 4. The computer system of claim 1, wherein the one or moreprograms further include instructions for: receiving, via the one ormore input devices, second authentication data; and in response toreceiving the second authentication data: in accordance with adetermination that the second authentication data satisfies theauthentication criteria associated with the account, displaying, via thedisplay generation component, a second machine-readable code associatedwith the account, wherein the second machine-readable code is differentfrom the first machine readable code; and in accordance with adetermination that the second authentication data does not satisfy theauthentication criteria associated with the account, forgoing display ofthe second machine-readable code associated with the account.
 5. Thecomputer system of claim 1, wherein the one or more programs furtherinclude instructions for: after displaying the machine-readable codeassociated with the account, ceasing to display the machine-readablecode after a predetermined amount of time.
 6. The computer system ofclaim 1, wherein the machine-readable code is a first machine-readablecode, and wherein the one or more programs further include instructionsfor: after displaying the first machine-readable code associated withthe account: ceasing to display the first machine-readable code after apredetermined amount of time; and displaying a second machine-readablecode associated with the account that is different from the firstmachine-readable code associated with the account.
 7. The computersystem of claim 1, wherein the one or more programs further includeinstructions for: after displaying the machine-readable code associatedwith the account: in accordance with a determination that secondauthentication data is received within a predetermined amount of timeand the second authentication data satisfies authentication criteriaassociated with the account, maintaining display of the machine-readablecode associated with the account; and in accordance with a determinationthat second authentication data is not received within the predeterminedamount of time or the second authentication data does not satisfy theauthentication criteria associated with the account, ceasing to displaythe machine-readable code associated with the account.
 8. The computersystem of claim 7, wherein the one or more programs further includeinstructions for: after displaying the machine-readable code associatedwith the account: in accordance with a determination that secondauthentication data is not received within the predetermined amount oftime or the second authentication data does not satisfy theauthentication criteria associated with the account, displaying arequest for the second authentication data.
 9. The computer system ofclaim 1, wherein the one or more programs further include instructionsfor: after displaying the machine-readable code associated with theaccount: receiving a confirmation that the machine-readable code wassuccessfully used to access information associated with the account; andin response to receiving the confirmation that the machine-readable codewas successfully used to access information associated with the account:ceasing to display the machine-readable code; and displaying, via thedisplay generation component, an indication that information associatedwith the account was successfully accessed.
 10. The computer system ofclaim 1, wherein displaying the machine-readable code includesdisplaying the machine-readable code at a first size, and wherein theone or more programs further include instructions for: while displayingthe machine-readable code at the first size, detecting a request todisplay the machine-readable code at a larger size; and in response todetecting the request to display the machine-readable code at a largersize, displaying the machine-readable code at a second size larger thanthe first size.
 11. The computer system of claim 1, wherein themachine-readable code is a machine readable code of a first type, andwherein the one or more programs further include instructions for: whiledisplaying the machine-readable code of the first type, detecting arequest to display a machine-readable code of a second type; and inresponse to detecting the request to display the machine-readable codeof the second type, displaying the machine-readable code of the secondtype.
 12. The computer system of claim 1, wherein displaying the firstuser interface includes displaying one or more offers associated withthe account.
 13. A non-transitory computer-readable storage mediumstoring one or more programs configured to be executed by one or moreprocessors of a computer system that is in communication with a displaygeneration component and one or more input devices, the one or moreprograms including instructions for: displaying, via the displaygeneration component, a first user interface including an indication ofan account; receiving, via the one or more input devices, authenticationdata; and in response to receiving the authentication data: inaccordance with a determination that the authentication data satisfiesauthentication criteria associated with the account, displaying, via thedisplay generation component, a first machine-readable code associatedwith the account; and in accordance with a determination that theauthentication data does not satisfy the authentication criteriaassociated with the account, forgoing display of the firstmachine-readable code associated with the account.
 14. A method,comprising: at a computer system that is in communication with a displaygeneration component and one or more input devices: displaying, via thedisplay generation component, a first user interface including anindication of an account; receiving, via the one or more input devices,authentication data; and in response to receiving the authenticationdata: in accordance with a determination that the authentication datasatisfies authentication criteria associated with the account,displaying, via the display generation component, a firstmachine-readable code associated with the account; and in accordancewith a determination that the authentication data does not satisfy theauthentication criteria associated with the account, forgoing display ofthe first machine-readable code associated with the account.